[
https://issues.jboss.org/browse/AS7-5063?page=com.atlassian.jira.plugin.s...
]
Rich DiCroce commented on AS7-5063:
-----------------------------------
I filed a bug report for EclipseLink regarding the race condition:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=388852
Apparently, although no bug report existed in the EclipseLink tracker, Oracle did have it
in their tracker for TopLink, which is based on EclipseLink. The bug is fixed in
EclipseLink trunk and the fix will be in the 2.4.1 release.
AS7 should pass the property "eclipselink.target-server =
JBoss" to persistence providers, or at least EclipseLink
------------------------------------------------------------------------------------------------------------------
Key: AS7-5063
URL:
https://issues.jboss.org/browse/AS7-5063
Project: Application Server 7
Issue Type: Enhancement
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Reporter: Craig Ringer
Assignee: Scott Marlow
Priority: Minor
Labels: eclipselink, jpa
Fix For: 7.2.0.Alpha1
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:
http://www.atlassian.com/software/jira