]
Scott Marlow updated JBAS-9040:
-------------------------------
Component/s: JPA / Hibernate
Support for pluggable JPA providers
-----------------------------------
Key: JBAS-9040
URL:
https://issues.jboss.org/browse/JBAS-9040
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: 7.0.0.CR1
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: