[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=12617545#comment-12617545 ] 

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

Documentation explaining how to package Hibernate3 jars for JPA use, will be added to above mentioned doc link.

http://community.jboss.org/thread/167590 describes how you can download a build with these changes.  

Although, I would rather see you download the AS7 source and build it yourself.  Test, fix problems that you run into (the AS7 code is easy/fun to play with).  More about this process is described in http://community.jboss.org/wiki/HackingOnAS7

If you want to try the code changes for this jira, before the doc is written, just add hibernate3 jars to your deployment and set the following property in your persistence unit (persistence.xml file):
<property name="jboss.as.jpa.providerModule" value="hibernate3-bundled"/>


> 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