Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: 7.0.1.Final
Component/s: JPA / Hibernate
Similar Issues:Show 10 results
AS7-647 pluggable JPA providers AS7-4194 Allow for pluggable user stores within realms AS7-5405 Initial Enterprise OSGi JPA implementation AS7-2233 JPA ClassTransformers are ignored AS7-2557 Provide JPA metrics within the console AS7-982 JPA Support for interposed synchronization AS7-5062 PersistenceUnitRootURL for JPA providers may not be spec compliant AS7-2459 JPA deployment support in EE client AS7-2419 Provide management use cases and operations of the JPA subsystem AS7-560 restructure use of JPA persistence provider specific details
Maybe we could have a service per persistence provider that is based on a configuration settings.
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)?