Well it should be possible as the PersistenceUnitManager is more a JPA Thing
and not restricted to Spring. In my example it is just configured using Spring.
Think it should be possible to do this an a JavaEE application (Perhaps I
should find this out somehow and extend my tutorial). If someone here knows how
to do so, I would be glad for some Input on this ;-)
Chris
Von: Stephen Connolly [stephen.alan.conno...@gmail.com]
Gesendet: Donnerstag, 11. Juli 2013 11:14
An: Maven Users List
Betreff: Re: Maven and JPA/EclipseLink Configuration...
That looks like a Spring only solution I wonder is there a pure JavaEE
counterpart
On 11 July 2013 09:56, christofer.d...@c-ware.de
christofer.d...@c-ware.dewrote:
You could have a look at my Wiki article about multiple persistence.xml
files:
https://dev.c-ware.de/confluence/display/PUBLIC/Multiple+persistence.xml+in+a+multi-module+application
Here you could separate your JPA entities from the platform dependent
Options. In your case you could create your persistence.xml files without
any db and application-server specific Settings and then simply add an
additional persistence.xml to your deployment ... the merging persistence
unit Manager would then merge those properties in automatically without
having to update all of the individual persistence.xml files.
Don't quite know why my confluence is so slow at the Moment ... will have
a look at this tonight.
Chris
Von: John Patrick [nhoj.patr...@gmail.com]
Gesendet: Dienstag, 9. Juli 2013 18:50
An: Maven Users List
Betreff: Maven and JPA/EclipseLink Configuration...
I'm working on a project that uses JPA EclipseLink, everything started of
fine with Jetty for developers development and WebLogic and Oracle proper
ear deployments.
EclipseLink has two values that need to be set in persistence.xml depending
upon your Application Server and Database;
eclipselink.target-server
eclipselink.target-database
This mean we have two profiles, Jetty and Release.
Now we support WebSphere and DB2, so have gone to 5 profiles and the need
to rebuild the ear 4 times which each profile.
Profiles
Jetty
WLSOracle
WLSDB2
WASOracle
WASDB2
I feel I'm doing something wrong...
Does someone have any suggestions on what to look at so i could potentially
build it once and get all the 4 ears build in one command? I've thought
about types or classifiers but unsure if that is just another hack...
Thoughts? As we soon might also need to support MySQL and Glassfish so
their is another 5 profiles and 5 more builds for a release.
John
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
