]
Leonardo Loch Zanivan commented on WFLY-203:
--------------------------------------------
I'm using WildFly 8.0.0 Alpha4 with Jipijapa EclipseLink 1.0.0 Alpha5 and still need
set JBoss enviroment variables below:
/system-property=eclipselink.target-server:add(value=org.jipijapa.eclipselink.JBossAS7ServerPlatform)
/system-property=eclipselink.archive.factory:add(value=org.jipijapa.eclipselink.JBossArchiveFactoryImpl)
The problem is that "eclipselink.logging.logger" stopped to work on WildFly,
that was OK on JBoss AS 7.2.0 Final.
PS: I'm using EclipseLink 2.5.0
add modules for Hibernate versions (3.x, 4.1.x/4.2.x), OpenJPA,
EclipseLink which contain the JipiJapa integration jars
-----------------------------------------------------------------------------------------------------------------------
Key: WFLY-203
URL:
https://issues.jboss.org/browse/WFLY-203
Project: WildFly
Issue Type: Enhancement
Components: JPA / Hibernate
Reporter: Craig Ringer
Assignee: Scott Marlow
Priority: Minor
Labels: eclipselink, jpa
Fix For: 8.0.0.Alpha2
For EclipseLink to properly identify the container and set up correct transaction
integration, etc, it needs the property "eclipselink.target-server" to be set to
"JBoss".
There's an open issue asking EclipseLink to auto detect the container
(
https://bugs.eclipse.org/bugs/show_bug.cgi?id=383257) but right now, a simple solution to
making EclipseLink work well on AS7 is for AS7 to pass that property to EclipseLink.
That'll help prevent issues and confusion like this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365704
Users can set it as a system property right now as shown on bug 383257, but really
it'd be best if JBoss passed it to the persistence unit during creation.
Time permitting I'll give this a go.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: