Adapt to JBoss AS 7 (with Spring managing the data sources) #1
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.
These changes are mostly in order to have Spring do all of the JPA persistence unit management on JBoss AS 7, as described in the documentation on porting Spring applications to JBoss AS 7 at https://docs.jboss.org/author/display/AS7/Spring+applications+development+and+migration+guide . This is only one possible approach. If, instead, it is desired that JBoss AS 7 manage the persistence units, Spring can be made to delegate to the container using the other technique described in that document.
There is also a bit of cleanup (mostly formatting, groupId, artifactId, etc.)
For convenience, I switched to HSQLDB, but that can certainly be changed back to PostgreSQL at any time.