[ https://issues.jboss.org/browse/AS7-4870?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-4870: ------------------------------ Fix Version/s: (was: 7.2.0.Alpha1) Description: jboss.as.jpa.providerModule is the name of the persistence provider module, that *could* be in a deployment descriptor so applications can change persistence providers more easily than messing with the persistence.xml (which defaults to the Hibernate module). Other deployment level options may make sense to include here as well. Originally this started with the idea of being targeted for Hibernate specifically, as a way to express which other modules are needed by Hibernate and for which purpose. That idea may come back (perhaps in a generic fashion). The persistence provider module dependencies could be { API extensions, service loader inverse dependencies, application modules} API extensions would be a module representing an API jar (could be merged with application modules), the application modules are the modules that should also be injected into the application deployment and the inverse service loader dependencies are just that. This part is on ice (see discussion in http://lists.jboss.org/pipermail/jboss-as7-dev/2012-May/005973.html). was: jboss.as.jpa.providerModule is the name of the persistence provider module, that should be in a deployment descriptor so applications can change modules with changing the persistence.xml (which defaults to the Hibernate module). jboss.as.jpa.adapterModule is the name of the integration classes that help AS to work with the persistence provider. Will try to hide this property rather than exposing it in the deployment descriptor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira