[jboss-jira] [JBoss JIRA] (AS7-3423) persistence providers deployed with applications should be available via javax.persistence.Persistence api

Scott Marlow (JIRA) jira-events at lists.jboss.org
Fri Feb 17 16:07:36 EST 2012


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

Scott Marlow commented on AS7-3423:
-----------------------------------

https://github.com/scottmarlow/jboss-as/tree/AS7-3423_deploymentWithJavaXPersistence_3 is work in progress (seems to be working but needs some cleanup)
                
> persistence providers deployed with applications should be available via javax.persistence.Persistence api
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-3423
>                 URL: https://issues.jboss.org/browse/AS7-3423
>             Project: Application Server 7
>          Issue Type: Task
>          Components: JPA / Hibernate
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 7.1.1.Final
>
>
> If an application deployment contains its own copy of a persistence provider and its own of the javax.persistence classes, deploy it as an application managed JPA application (no container managed JPA support feature are expected to be used).
> 1.  initialize the application copy of the javax.persistence.Persistence class by setting an application deployment level PersistenceProviderResolver (via javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver()) that would know about the persistence provider that is bundled.
> 2.  don't inject the javax.persistence module into the deployment.
> 3.  add a unit test that bundles a persistence provider, javax.persistence classes and uses javax.persistence.Persistence.createEntityManagerFactory(String persistenceUnitName).
> https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might be worth looking at when this jira is worked around.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list