-
Sub-task
-
Resolution: Done
-
Major
-
None
-
None
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.
3. How could we best dynamically build a ModuleDependency on a persistence provider jar that
could be injected into a deployment (perhaps from JPADependencyProcessor)?
- blocks
-
AS7-388 Detect, filter, and act upon system APIs found in deployments
- Resolved
-
AS7-413 Rename "jboss-structure.xml" to "jboss-deployment-structure.xml"
- Resolved
- is related to
-
AS7-560 restructure use of JPA persistence provider specific details
- Closed
- relates to
-
AS7-574 Deploy compatible versions of the Hibernate persistence provider with application deployments
- Closed