Re: [eclipselink-dev] Re: PersistenceProvider.createContainerEntityManag

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Phillip,

  Thanks for the info.

  How is createContainerEntityManagerFactory() called?  I assume it is called 
by Spring, but it is not clear to me how it gets our OSGi version of the 
persistence provider (rather than the normal SPI-based one)

  I discussed this issue with some of the folks around here and we all agree 
that this is something we want to support as soon as we can fit some engineering 
time in to work through the issues and we'd be interested to know what issues 
you are encountering.

  One thing we are unsure about is how JTA transactions will work in an OSGi 
world.  In a container-managed JPA deployment, we use JNDI to get the 
transaction manager.  You mentioned that you had things working with a subclass 
of our PersistenceProvider.  Do transactions work when you run like that?

-Tom

Philipp Nanz wrote:
> Hi Tom,
>
> I'm using Spring's LocalContainerEntityManagerFactoryBean, which 
> supposedly implements the JPA container contract and works very well 
> with the non-OSGi EclipseLink PersistenceProvider.
>
> This factory doesn't know anything about OSGi so if you (EclipseLink) 
> expect something special in an OSGi environment it will not be of help. 
> Then again I do not quite understand what that could possibly be.
>
> As far as I'm concerned the container contract as it is implemented 
> today for the non-OSGi PersistenceProvider would work well enough in the 
> OSGi environment.
>
> Kind regards,
> Philipp