Jpaming #2
Open
Jpaming #2
+601
−72
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 21 commits
January 25, 2012 09:40
lack of converters
correctly, and adding a parameter to the view so that it can be told to focus on a particular student.
some early testing of the wiring of the students view.
and filled in the code for creating a simple sample database.
inadvertent little transaction mistakes.
view (i.e. allow a parameter to be passed about the student to edit, alter database access to use the StudentRegistry, etc.)
Conflicts: WebContent/WEB-INF/web.xml WebContent/templates/basicTemplate.xhtml WebContent/views/student/basic.xhtml src/main/java/ca/openstudent/Student.java src/main/java/ca/openstudent/bean/StudentBean.java src/main/resources/META-INF/persistence.xml
efficiency, but that set needs to later be changed into a list so that it can be used by JSF.
|
This is great. I am going to checkout and test over this weekend. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So I've made a branch with an example of what I was thinking of in terms of accessing JPA directly. You need to grab a derby.jar to use the code because it stores all the data in an in-memory derby database (as opposed to storing things in-memory in an ArrayList). I've rewired the search stuff to use JPA, and I've wired up the creation of new students and editing of students (but only through the (debug) list all students view). You don't have to merge this in (in particular, I had to temporarily disable logins in web.xml so that I could test things); I'm just sending it to you as an example of one way of formatting everything.