Hi,
It did not work in 7.1.0.Alpha
20:59:49,478 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 6) Deployment of "aglite-nonosgiweb.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"aglite-nonosgiweb.war#aglite-platform-persistence-unit\" missing [jboss.naming.context.java.com.arisglobal.aglite.datasource.agliteDS ]"]}
20:59:49,661 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Stopped deployment aglite-nonosgiweb.war in 184ms
<persistence-unit name="aglite-platform-persistence-unit" transaction-type="RESOURCE_LOCAL">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
Persistence.xml does not have the <non-jta-datasource>.
We want full control over the way persistence units are managed. To give you a context of why we are doing things this way:-
We don't have the entity classes specified within our persistence XML file. What we are building is a platform which allows applications to be plugged into it. The entity classes will be pushed at runtime through a Spring bean factory post processor. We also need to allow muliple datasources which could be configured per application/customer (user group). We also create entity managers and transacton managers on the fly based on application/customer configuration.
Thus a hardcoded datasource approach won't work for us.