Patrick Linskey wrote:
This means that your container would be responsible for EntityManager
lifecycle and potentially for transaction control. It also means that
you'd interact with OpenJPA via the
PersistenceProvider.createContainerEntityManagerFactory() API. In such
a scenario, you (the
That sounds like the right way to do it. So my container would, on
startup, instantiate OpenJPA's PersistenceProviderImpl, and invoke
createContainerEntityManagerFactory() with a PersistenceUnitInfo that I
implement?
Yes. Note that OpenJPA already has an PUInfo implementation that you
might
Hello,
I'm planning on embedding OpenJPA in a server (which is running in a
J2EE environment). OpenJPA will run entirely within this server, and
together with added functionality implement a content container in
which entities can be depolyed, just as servlets can in a servlet container.
So
here and there to support additional
features.
-Patrick
On 5/14/07, Dennis Thrysøe [EMAIL PROTECTED] wrote:
Hello,
I'm planning on embedding OpenJPA in a server (which is running in a
J2EE environment). OpenJPA will run entirely within this server, and
together with added functionality implement
