Hi Sanne,
There is a manual step, that is somewhat in flux, as I look for the best
approach (I don't expect any of this to work completely, I'm just fixing
issues as I go). The manual step, is:
1. After building AS7 from source, create folder
jboss-as-7.1.0.Alpha1-SNAPSHOT/modules/org/hibernate/ogm.
2. In the above ogm folder, I copied in
hibernate-ogm-core-3.0.0-SNAPSHOT.jar and created a module.xml file with
contents
http://pastie.org/2350230
3. I also created a
jboss-as-7.1.0.Alpha1-SNAPSHOT/modules/org/hibernate/3 folder with the
following jars in it:
antlr-2.7.6.jar, commons-collections-3.1.jar, commons-digester.jar,
hibernate3.jar, log4j.jar, commons-collections.jar, dom4j-1.6.1.jar,
jta-1.1.jar, commons-beanutils.jar, javassist-3.12.0.GA.jar
4. Created a module.xml file in folder
jboss-as-7.1.0.Alpha1-SNAPSHOT/modules/org/hibernate/3 with contents
http://pastie.org/2350323
The above creates the hibernate:ogm module and hibernate:3 module.
I committed the test case to
https://github.com/scottmarlow/jboss-as/tree/ogm.
To run the test, "cd as7/testsuite/compat" and "mvn clean install
-DallTests"
On 08/10/2011 08:23 AM, Sanne Grinovero wrote:
Hi Scott,
I've been trying to run your test: got a fresh checkout of jboss-as,
and pasted your test in testsuite/compat as suggested by your package
name choice.
Running from command line, I get:
Tests in error:
org.jboss.as.testsuite.compat.jpa.hibernate.OGMHibernate3SharedModuleProviderTestCase:
Could not start container
and the test logs contain as ultimate cause
Caused by: java.lang.IllegalStateException: Cannot find:
target/jbossas/jboss-modules.jar
at
org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:94)
... 67 more
Any hints?
Anyway, I just wanted to check if I could fix the issue by changing
the configuration settings in persistence.xml:
generally you should remove the<jta-data-source>: no datasource is
used. Also properties like "hibernate.show_sql" are not meaningfull,
and it should not be needed to specify the Noop Dialect anymore.
I tried again with these changes, however, commenting out the datasource
is currently not handled (AS7 JPA container/subsystem gets confused).
If I add the datasource back in, I get the "No Dialect mapping for JDBC
type: 4" error.
I assume its important for me not to pass in the datasource? Just want
to confirm before changing AS7 code for that. :)
Current Hibernate OGM is depending on Hibernate Core 3.6.5, so I just
checked and upgrade to 3.6.6: all tests still pass, so I would expect
that should not be a problem.
Is specifying "jboss.as.jpa.providerModule" all what is needed to get
OGM on my classpath? that might be the problem for me: not sure if I
have this module somehow, I just cloned jboss-as upstream (as I've
seen the pull request you mentioned was already included).
Sanne
2011/8/10 Scott Marlow<smarlow(a)redhat.com>:
> Hi,
>
> I'm playing with OGM on AS7, well trying to. I currently am trying to
> use Hibernate 3.6.6.Final, latest OGM master source, latest AS7 master
> source (plus these changes
https://github.com/jbossas/jboss-as/pull/138).
>
> I'm getting a "No Dialect mapping for JDBC type: 4" error during
> deployment
http://pastie.org/2348064
>
> Should I be using an earlier version of Hibernate 3.x perhaps?
>
> Test code is here
http://pastie.org/2348071 (contains persistence.xml
> inline).
>
> Thanks,
> Scott
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>