[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-260) Initial JPA implementation

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714843#comment-12714843 ] 

Scott Marlow commented on JBOSGI-260:
-------------------------------------

If HHH-7527 is about adding OSGi support to Hibernate ORM and AS7-5405 is about supporting the OSGi Enterprise JPA specification.  Which work is this jira for?  

Can OSGi Enterprise JPA use EE JPA (container) support or do we need a new subsystem for OSGi JPA?  Does OSGi require a dynamic implementation of PersistenceProviderResolver (that could change Hibernate/EclipseLink/OpenJPA/other providers on the fly)?  I thought that was required but I don't see it in the OSGi Enterprise Release 5 pdf that I'm looking at.

{quote}We are most definitely not going to support multiple competing JPA providers in AS7.{quote} I assume you mean with respect to what is possible with OSGi.  On the EE side, we need to support different persistence providers for various reasons (e.g. EE TCK compliance testing).  Another reason to support EclipseLink, is for migrations.  It is easier to migrate an application to run on JBoss AS, if you don't have to switch persistence providers right away.  
                
> Initial JPA implementation
> --------------------------
>
>                 Key: JBOSGI-260
>                 URL: https://issues.jboss.org/browse/JBOSGI-260
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JPA/JDBC
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: JBossOSGi 2.0.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira