Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt to JBoss AS 7 (with Spring managing the data sources) #1

Merged
merged 5 commits into from
Oct 10, 2012

Conversation

cortextual
Copy link
Contributor

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.

…comment out PostgreSQL JDBC driver (not using PostgreSQL at this point); correct the project name and remove WAR file override
… to the presence of JPA annotations -- we're using Hibernate 3.
… that JBoss's JPA subsystem won't see it. Also switch to HSQLDB for now for simplicity.
lpintosil added a commit that referenced this pull request Oct 10, 2012
Adapt to JBoss AS 7 (with Spring managing the data sources)
@lpintosil lpintosil merged commit 030d30f into lpintosil:master Oct 10, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants