Charles Miller [
http://community.jboss.org/people/charleswmiller] created the discussion
"Re: AS 7 Persistence Provider Problem"
To view the discussion, visit:
http://community.jboss.org/message/629048#629048
--------------------------------------------------------------
Ok, here is what I've got so far... Checking in to confirm/deny your last post made
sense.
*1)* Simple module defintion in the as7/modules/org/eclipse/persistence folder - there
might be more dependencies but so far it seems the eclipselink jar is pretty much
standalone.
<module xmlns="urn:jboss:module:1.0"
name="org.eclipse.persistence">
<resources>
<resource-root path="eclipselink.jar"/>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
*2)* I have taken some notes locally related to how the module was created. I'm not
sure the best way to integrate into documentation. I guess when things actually work, it
should be pretty easy.
*3)* I've hacked the following classes based upon the Hibernate jpa package.
Basically, everywhere I see "Hibernate", replace with "Eclipselink" --
working through the details for swapping out differences in implementation details for
Eclipselink
<package - structure>
<integration><jpa>
<eclipselink>
- Employee
- SessionFactoryTestCase
- SFSB1
-SFSBEclipselinkSession
-SFSBEclipselinkSessionFactory
*Question*:
Does the following properties entry go into the "standalone.xml"? - The
Hibernate entry in standalone seems pretty involved - will the entry in the standalone.xml
be simular for eclipselink?
<properties>
<property name="jboss.as.jpa.providerModule"
value="org.eclipse.persistence" />
</properties>
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/629048#629048]
Start a new discussion in JBoss AS7 Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]