Hi,Note that it'd be sufficient to just create an EntityManager and then close it.
I believe that we have a JIRA issue tracking the addition of a property that fully initializes things when the EMF is configured, rather than when the first EM is created.
FYI, this isn't how things work by default because we can't know whether or not data sources and classloaders and whatnot are all properly available when an EMF is configured; many deployment environments want to configure everything in some arbitrary order and expect that one configuration operation won't depend on a separate component configuration having happened.
-Patrick On Jun 25, 2008, at 1:38 AM, Enrico Goosen wrote:
My colleague suggested a simple solution, which works fine.I just call a query from my init servlet (load-on-startup="0"), and thatstarts up OpenJPA, so when my client (GWT) calls a service, OpenJPA is already initialized. -- View this message in context: http://www.nabble.com/Starting-OpenJPA-during-container-startup-tp18096595p18107481.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
-- Patrick Linskey 202 669 5907
smime.p7s
Description: S/MIME cryptographic signature
