[
https://issues.jboss.org/browse/AS7-566?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on AS7-566:
----------------------------------
Will need a jboss-deployment-structure.xml rather than MANIFEST.MF entries. Also need one
more change for locating PersistenceProviderAdaptor implementations (the integration
classes). Will need a META-INF/services entry in each of the integration modules.
services/org.jboss.as.jpa.spi.PersistenceProviderAdaptor
org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="org.hibernate"/>
</exclusions>
<dependencies>
<module name="org.jboss.as.jpa.hibernate3"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
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