[jboss-jira] [JBoss JIRA] Commented: (AS7-566) Support for pluggable JPA providers

[Scott Marlow (JIRA)]

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

Scott Marlow commented on AS7-566:
----------------------------------

Committed some changes here https://github.com/scottmarlow/jboss-as/commit/18633d5c1f7dcb8e6e7f135b171eddacbbe659a2 and https://github.com/scottmarlow/jboss-as/commit/6b9aef5eac3c1c97db6d8cff66b735cf6d2f0821

Am currently working on the Hibernate3 module for AS7.  If everything goes as planned, JPA applications that include a copy of Hibernate 3 jars, will need to add a dependency on the "org.jboss.as.jpa.hibernate3" module (as described in https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7).  This could be done by adding a MANIFEST.MF entry:
Dependencies: org.jboss.as.jpa.hibernate3

Or something like the above, depending on how this effort goes.  :-)



> Support for pluggable JPA providers
> -----------------------------------
>
>                 Key: AS7-566
>                 URL: https://issues.jboss.org/browse/AS7-566
>             Project: Application Server 7
>          Issue Type: Sub-task
>          Components: JPA / Hibernate
>            Reporter: David Lloyd
>            Assignee: Scott Marlow
>             Fix For: 7.1.0.Alpha1
>
>
> Maybe we could have a service per persistence provider that is based on a configuration settings.
> Questions:
> 1.  Where do the persistent provider jars go in the system?  Should we deploy them somehow?
> 2.  Each persistence.xml specifies the javax.persistence.spi.PersistenceProvider class name (via provider element) that it will use (defaults to whatever the AS7 default persistence provider).  The persistence.xml also allows vendor properties to be specified.  We could have an optional property "org.jboss.jpa.provider.versionSpecifier" that matches a specific version of the provider.
> Is this the best way to allow different versions of persistence provider?
> 3.  How could we best dynamically build a ModuleDependency on a persistence provider jar that 
> could be injected into a deployment (perhaps from JPADependencyProcessor)?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira