AS 7 currently does not know how to deploy alternative JPA provider and Hibernate OGM is one.
Scott is looking at this.
Marko, are you building AS7 from source? I put a patch together (https://github.com/jbossas/jboss-as/pull/138) that should get pulled into either AS 7.0.1 or 7.1. The patch should address the deployment exception. If your building from AS7 source, I can point out the (git) commits that you would need to cherry-pick.
no i got it from nightly build ( hudson )
The needed AS7 changes were merged into the AS7 master git repository last night.
Some success today with the latest OGM (you will need Sanne's OGM fix from today). I created an as7/modules/org/hibernate/ogm folder with the hibernate-ogm-core-3.0.0-SNAPSHOT.jar and module.xml (see http://pastie.org/2353169 for the contents). I also created an as7/modules/org/hibernate/3 folder as is already known how to do (https://docs.jboss.org/author/display/AS7/JPA+Reference+Guide).
The test case is very simple and is run after manually applying the above changes to a freshly built AS7. https://github.com/scottmarlow/jboss-as/blob/ogm/testsuite/compat/src/test/java/org/jboss/as/testsuite/compat/jpa/hibernate/OGMHibernate3SharedModuleProviderTestCase.java
I ran the test and captured the server.log output here http://pastie.org/2353229. Not much to see but could be interesting for comparing to what you see in your server.log.
I have one app using cassandra as database.
It worked with JBoss AS 7.0.0, but i tried 7.0.2 and:
22:22:24,670 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found oqi-web.war in deployment directory. To trigger deployment create a file called oqi-web.war.dodeploy
22:22:24,685 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "oqi-web.war"
22:22:25,846 INFO [org.jboss.as.jpa] (MSC service thread 1-9) added javax.persistence.api dependency to oqi-web.war
22:22:26,094 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC00001: Failed to start service jboss.deployment.unit."oqi-web.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."oqi-web.war".INSTALL: Failed to process phase INSTALL of deployment "oqi-web.war"
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.6.0_26]
at java.lang.Thread.run(Unknown Source) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: only one persistence provider can be packaged with an application [org.apache.openjpa.persistence.PersistenceProviderImpl, me.prettyprint.hom.CassandraPersistenceProvider]
... 5 more
Jira AS7-2046 represents this issue. I was wrong about it being fixed already. The workaround is to package the desired provider as a module.
Sorry, i didnt have enough time to test, but as your last post says, i will need to create a module and configure it under standalone-preview.xml, right?
If your trying trying to use OpenJPA, watch thread http://community.jboss.org/thread/173967 to learn more about the community effort to integrate that.
For some examples of creating a module for a persistence provider read http://in.relation.to/Bloggers/UsingADifferentPersistenceProviderWithAS701