eclipselink-dev

[eclipselink-dev] Check in for Bug 296010 Getting nullpointer during starting of javax.persistence

shaun.smith@xxxxxxx (Shaun Smith) — Thu, 26 Nov 2009 19:37:04 GMT

https://bugs.eclipse.org/bugs/show_bug.cgi?id=296010

When the javax.persistence bundle was started after o.e.p.jpa, an NPE occurred when the EclipseLink Persistence Provider service was found and attempted to be registered. The map of registered providers was uninitialized which resulted in an NPE.

Tested both manually and with OSGi SRG.

Reviewed by Tom Ware

--

Shaun Smith | Principal Product Manager
Phone: +19055023094
Oracle Server Technologies, Oracle TopLink
ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga, Ontario | L5R 3P4
Oracle is committed to developing practices and products that help protect the environment

[eclipselink-dev] EclipseLink 2.1.0 Feature Planning

PETER.KROGH@xxxxxxx (Peter Krogh) — Thu, 26 Nov 2009 18:30:38 GMT

Hi All,

The EclipseLink project is starting to plan feature work for its 2.1.0 release, and we are asking for your help.  Please let us know what features you would like to see added to EclipseLink.  The best way to do this is through bugzilla.

If you want to see a particular new feature added to EclipseLink, please search for it in bugzilla.
	If there is not a current enhancement request tracking your issue, add it and vote for it.
	If you see an existing enhancement request that you would like to see in 2.1.0 please vote for it.

Thank you in advance for your participation in 2.1.0.

Peter Krogh

[eclipselink-dev] BUILD STATUS:: trunk cb build has test failures!

eric.gwin@xxxxxxx (eric . gwin) — Thu, 26 Nov 2009 17:20:04 GMT

Build summary for 2.0.0.v20091126-r5904
-----------------------------------
TEST-CORE-SRG
  Tests run:683 Failures:0 Errors:0
TEST-JPA-SRG
  Tests run:192 Failures:0 Errors:0
TEST-MOXY-SRG
  Tests run:458 Failures:0 Errors:5
TEST-SDO-SRG
  Tests run:120 Failures:0 Errors:0
TEST-DBWS-SRG
  Tests run:14 Failures:0 Errors:0
TEST-DBWS-UTILS-SRG
  Tests run:22 Failures:0 Errors:0
-----------------------------------

Build log: (/shared/rt/eclipselink/logs/bsb-trunk_cb_091126-1200.log)
    
Build logs can be found on the download server at:
    http://www.eclipse.org/eclipselink/downloads/build-failures.php
-----------------------------------

SVN Changes since Last Build:
------------------------------------------------------------------------
r5904 | bdoughan | 2009-11-26 11:10:40 -0500 (Thu, 26 Nov 2009)
Changed paths:
   M /trunk/moxy/eclipselink.moxy.test/src/org/eclipse/persistence/testing/oxm/mappings/XMLMappingTestCases.java
   M /trunk/moxy/eclipselink.moxy.test/src/org/eclipse/persistence/testing/oxm/mappings/namespaces/ExtraNamespacesBug6004272TestCases.java
   M /trunk/moxy/eclipselink.moxy.test/src/org/eclipse/persistence/testing/oxm/mappings/simpletypes/documentpreservation/DocumentPreservationTestCases.java
------------------------------------------------------------------------

Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver

yiping.zhao@xxxxxxx (yiping zhao) — Thu, 26 Nov 2009 15:48:35 GMT

Hi Tom,

We did find the test error on other servers, but we haven't had time to fix it yet. so the testcase needs to be fixed like:

// this may fail with some drivers
           int result = 0;
           try {
               result = query1.executeUpdate();
           } catch (RuntimeException ex) {
               rollbackTransaction(em);
               closeEntityManager(em);
               em = createEntityManager();
               beginTransaction(em);
           }

Yiping

On 11/26/2009 10:10 AM, Tom Ware wrote:

If the entity manager is transaction scoped, I think Sabine is right. The entity manager should be closed when the transaction either commits or rolls back. I wonder why that is not happening on other servers. (you'll notice query1.executeUpdate() is designed to fail)
-Tom
yiping zhao wrote:
Hi Sabine,
In the test framework, by default the entity manager is injected in sessionbean, it's transaction-scoped.

>From the stacktrace, it looks like that there is issue when executing "result = query1.executeUpdate();", then somehow your SAP NetWeaver application server closes the entity manager, after that you get the exception "java.lang.IllegalStateException: Attempting to execute an operation on a closed EntityManager" when executing "query2.executeUpdate();", so this sounds like a server issue.
Yiping
On 11/26/2009 4:34 AM, Heider, Sabine wrote:
Hi Tom,
I'm not really familiar with the details of test framework either, but I guess the entity manager is taken from the TestRunnerBean:

@Stateless(name="TestRunner", mappedName="TestRunner") @Remote(TestRunner.class) @TransactionManagement(TransactionManagementType.BEAN) public class TestRunnerBean implements TestRunner { /** The entity manager for the test is injected and passed to the test server platform. */ @PersistenceContext private EntityManager entityManager;

/** The entity manager factory for the test is injected and passed to the test server platform. */ @PersistenceUnit private EntityManagerFactory entityManagerFactory;
So yes, it is transaction-scoped.
Best regards,
Sabine
-----Original Message----- From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware Sent: Mittwoch, 25. November 2009 14:07 To: Dev mailing list for Eclipse Persistence Services Subject: Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver
Hi Sabine,
I am not familiar with how the entity manager for the tests are created. The part of the spec you are referring to is for Transaction-scoped entity managers. Is the entity manager used in this test created in such a way that it will be transaction-scoped on all servers?
-Tom
Heider, Sabine wrote:
Hi, I'd like to get your opinion on an error I get when running the JPA server tests inside an SAP NetWeaver application server (stack shortened, executed on current trunk): java.lang.IllegalStateException: Attempting to execute an operation on a closed EntityManager. at org.eclipse.persistence.internal.jpa.EntityManagerImpl.verifyOpen(EntityManagerImpl.java:1516)

at org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeUpdate(EJBQueryImpl.java:492)

at org.eclipse.persistence.testing.tests.jpa.relationships.EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL(EMQueryJUnitTestSuite.java:121)

at org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareServer(JUnitTestCase.java:463)

at org.eclipse.persistence.testing.framework.server.TestRunnerBean.runTest(TestRunnerBean.java:87)

I run the test against a MySQL database. The MySQL driver throws an SQLException in EMQueryJUnitTestSuite line 114: Can not issue executeUpdate() for SELECTs. Consequently, I end up in the catch block where the current transaction is rolled back. Chapter 7.9.1 of the JPA specification says: "After the JTA transaction has completed (either by transaction commit or rollback), The container closes the entity manager by calling EntityManager.close." Apparently, this is what the JPA container in NetWeaver does. With the closed entity manager, however, query2 becomes unusable. In my opinion, it's an error of the test rather than of the JPA container, but I might be wrong. What do you think? Thanks and best regards, Sabine *Sabine Heider **SAP AG

*Pflichtangaben/Mandatory Disclosure Statements: _http://www.sap.com/company/legal/impressum.epx_

------------------------------------------------------------------------

_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-dev _______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
------------------------------------------------------------------------
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver

tom.ware@xxxxxxx (Tom Ware) — Thu, 26 Nov 2009 15:11:10 GMT

If the entity manager is transaction scoped, I think Sabine is right. The entity manager should be closed when the transaction either commits or rolls back. I wonder why that is not happening on other servers. (you'll notice query1.executeUpdate() is designed to fail)

-Tom

yiping zhao wrote:

Hi Sabine,
In the test framework, by default the entity manager is injected in sessionbean, it's transaction-scoped.

>From the stacktrace, it looks like that there is issue when executing "result = query1.executeUpdate();", then somehow your SAP NetWeaver application server closes the entity manager, after that you get the exception "java.lang.IllegalStateException: Attempting to execute an operation on a closed EntityManager" when executing "query2.executeUpdate();", so this sounds like a server issue.
Yiping
On 11/26/2009 4:34 AM, Heider, Sabine wrote:
Hi Tom,
I'm not really familiar with the details of test framework either, but I guess the entity manager is taken from the TestRunnerBean:
@Stateless(name="TestRunner", mappedName="TestRunner") @Remote(TestRunner.class) @TransactionManagement(TransactionManagementType.BEAN) public class TestRunnerBean implements TestRunner { /** The entity manager for the test is injected and passed to the test server platform. */ @PersistenceContext private EntityManager entityManager;
    /** The entity manager factory for the test is injected and passed to the test server platform. */
    @PersistenceUnit
    private EntityManagerFactory entityManagerFactory;
So yes, it is transaction-scoped.
Best regards,
Sabine
-----Original Message-----
From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
Sent: Mittwoch, 25. November 2009 14:07
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver
Hi Sabine,
I am not familiar with how the entity manager for the tests are created. The part of the spec you are referring to is for Transaction-scoped entity managers. Is the entity manager used in this test created in such a way that it will be transaction-scoped on all servers?
-Tom
Heider, Sabine wrote:
Hi, I'd like to get your opinion on an error I get when running the JPA server tests inside an SAP NetWeaver application server (stack shortened, executed on current trunk): java.lang.IllegalStateException: Attempting to execute an operation on a closed EntityManager. at org.eclipse.persistence.internal.jpa.EntityManagerImpl.verifyOpen(EntityManagerImpl.java:1516) at org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeUpdate(EJBQueryImpl.java:492) at org.eclipse.persistence.testing.tests.jpa.relationships.EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL(EMQueryJUnitTestSuite.java:121) at org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareServer(JUnitTestCase.java:463) at org.eclipse.persistence.testing.framework.server.TestRunnerBean.runTest(TestRunnerBean.java:87) I run the test against a MySQL database. The MySQL driver throws an SQLException in EMQueryJUnitTestSuite line 114: Can not issue executeUpdate() for SELECTs. Consequently, I end up in the catch block where the current transaction is rolled back. Chapter 7.9.1 of the JPA specification says: "After the JTA transaction has completed (either by transaction commit or rollback), The container closes the entity manager by calling EntityManager.close." Apparently, this is what the JPA container in NetWeaver does. With the closed entity manager, however, query2 becomes unusable. In my opinion, it's an error of the test rather than of the JPA container, but I might be wrong. What do you think? Thanks and best regards, Sabine *Sabine Heider **SAP AG

*Pflichtangaben/Mandatory Disclosure Statements: _http://www.sap.com/company/legal/impressum.epx_
------------------------------------------------------------------------
_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-dev _______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
------------------------------------------------------------------------
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver

yiping.zhao@xxxxxxx (yiping zhao) — Thu, 26 Nov 2009 15:01:24 GMT

Hi Sabine,

In the test framework, by default the entity manager is injected in sessionbean, it's transaction-scoped.

>From the stacktrace, it looks like that there is issue when executing "result = query1.executeUpdate();", then somehow your SAP NetWeaver application server closes the entity manager, after that you get the exception "java.lang.IllegalStateException: Attempting to execute an operation on a closed EntityManager" when executing "query2.executeUpdate();", so this sounds like a server issue.

Yiping

On 11/26/2009 4:34 AM, Heider, Sabine wrote:

Hi Tom,

I'm not really familiar with the details of test framework either, but I guess the entity manager is taken from the TestRunnerBean:

@Stateless(name="TestRunner", mappedName="TestRunner")
@Remote(TestRunner.class)
@TransactionManagement(TransactionManagementType.BEAN)
public class TestRunnerBean implements TestRunner {
    
    /** The entity manager for the test is injected and passed to the test server platform. */
    @PersistenceContext
    private EntityManager entityManager;

    /** The entity manager factory for the test is injected and passed to the test server platform. */
    @PersistenceUnit
    private EntityManagerFactory entityManagerFactory;

So yes, it is transaction-scoped. 

Best regards,
Sabine

-----Original Message-----
From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
Sent: Mittwoch, 25. November 2009 14:07
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver

Hi Sabine,

   I am not familiar with how the entity manager for the tests are created.  The 
part of the spec you are referring to is for Transaction-scoped entity managers. 
  Is the entity manager used in this test created in such a way that it will be 
transaction-scoped on all servers?

-Tom

Heider, Sabine wrote:

Hi,
 
I'd like to get your opinion on an error I get when running the JPA 
server tests inside an SAP NetWeaver application server (stack 
shortened, executed on current trunk):
 
java.lang.IllegalStateException: Attempting to execute an operation on a 
closed EntityManager.
at 
org.eclipse.persistence.internal.jpa.EntityManagerImpl.verifyOpen(EntityManagerImpl.java:1516)
at 
org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeUpdate(EJBQueryImpl.java:492)
at 
org.eclipse.persistence.testing.tests.jpa.relationships.EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL(EMQueryJUnitTestSuite.java:121)
at 
org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareServer(JUnitTestCase.java:463)
at 
org.eclipse.persistence.testing.framework.server.TestRunnerBean.runTest(TestRunnerBean.java:87)
 
I run the test against a MySQL database. The MySQL driver throws an 
SQLException in EMQueryJUnitTestSuite line 114: Can not issue 
executeUpdate() for SELECTs.
Consequently, I end up in the catch block where the current transaction 
is rolled back.
 
Chapter 7.9.1 of the JPA specification says:
"After the JTA transaction has completed (either by transaction commit 
or rollback), The container
closes the entity manager by calling EntityManager.close."
 
Apparently, this is what the JPA container in NetWeaver does. With the 
closed entity manager, however, query2 becomes unusable.
 
In my opinion, it's an error of the test rather than of the JPA 
container, but I might be wrong. What do you think?
 
Thanks and best regards,
Sabine
 
*Sabine Heider
**SAP AG

*Pflichtangaben/Mandatory Disclosure Statements:
_http://www.sap.com/company/legal/impressum.epx_
 
 
 


------------------------------------------------------------------------

_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

[eclipselink-dev] Expanding 'standards' for build files.

eric.gwin@xxxxxxx (Eric Gwin) — Thu, 26 Nov 2009 13:06:49 GMT

Hi,

I'm sending this out as a notification/proposal of some additional standard conventions I plan on adding to our build files after the branch. - properties ending in .jar define jarfile names only (no path) - properties ending in .lib are fully qualified jars (path and filename) - properties ending in .dir are directory paths - properties ending in .path are path refid names (classpath fragments) - targets beginning with test- are reserved for high level test targets, and are used in test results parsing - targets typically use the form -- (ie. package-bundle-zip)

Some are clarifications of standards already in place, but not well publicized. However, with regard to .jar/.lib and .dir/.path there is no current standard, and properties are named and used in a fairly random mostly interchangeable way. There are many reasons this is becoming an issue now, but here are the biggest: - bugs requesting the use of minimal classpaths necessitate the need to individually define libraries. However, the build has multiple entry points so paths to those libraries are relative to the entry point. So the need to separate path from jar name. - adding individual libraries (rather than eclipselink.core.depend or eclipslink.oracle.depend which list them all) also creates a need to separately define directories and classpath subsets.

For the most part I've tried to keep the usage most prevalent for each postfix -.lib was mostly used to define full paths to jars, while .jar mostly defined jar names. However, there are also a few non-conformant properties (eclipselink.jar.name and .jarfile) -.dir really hasn't changed at all, but there were a few uses where it was a defining a pathref -.path is pretty much new old pathrefs were either .dir or .classpath

While I needed to implement these changes for the oracle modules for critical fixes in 2.0.0, I plan on implementing these changes across the board after the branch and discussion has occurred.

Does anyone object to these standards, or have preferences other than what I plan to implement? I can see .jarfile being used as the standard postfix because the property can't easily be confused with a static usage of a jar, but it wasn't routinely used.

Comments? (If I hear nothing from you I will assume it is assent, and continue as outlined after the branch is complete.)

-Eric

RE: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver

sabine.heider@xxxxxxx (Heider, Sabine) — Thu, 26 Nov 2009 09:34:30 GMT

Hi Tom,

I'm not really familiar with the details of test framework either, but I guess the entity manager is taken from the TestRunnerBean:

@Stateless(name="TestRunner", mappedName="TestRunner")
@Remote(TestRunner.class)
@TransactionManagement(TransactionManagementType.BEAN)
public class TestRunnerBean implements TestRunner {
    
    /** The entity manager for the test is injected and passed to the test server platform. */
    @PersistenceContext
    private EntityManager entityManager;

    /** The entity manager factory for the test is injected and passed to the test server platform. */
    @PersistenceUnit
    private EntityManagerFactory entityManagerFactory;

So yes, it is transaction-scoped. 

Best regards,
Sabine

-----Original Message-----
From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
Sent: Mittwoch, 25. November 2009 14:07
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Error in EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL on SAP NetWeaver

Hi Sabine,

   I am not familiar with how the entity manager for the tests are created.  The 
part of the spec you are referring to is for Transaction-scoped entity managers. 
  Is the entity manager used in this test created in such a way that it will be 
transaction-scoped on all servers?

-Tom

Heider, Sabine wrote:
> Hi,
>  
> I'd like to get your opinion on an error I get when running the JPA 
> server tests inside an SAP NetWeaver application server (stack 
> shortened, executed on current trunk):
>  
> java.lang.IllegalStateException: Attempting to execute an operation on a 
> closed EntityManager.
> at 
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.verifyOpen(EntityManagerImpl.java:1516)
> at 
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeUpdate(EJBQueryImpl.java:492)
> at 
> org.eclipse.persistence.testing.tests.jpa.relationships.EMQueryJUnitTestSuite.testcreateNativeQueryWithSelectSQL(EMQueryJUnitTestSuite.java:121)
> at 
> org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareServer(JUnitTestCase.java:463)
> at 
> org.eclipse.persistence.testing.framework.server.TestRunnerBean.runTest(TestRunnerBean.java:87)
>  
> I run the test against a MySQL database. The MySQL driver throws an 
> SQLException in EMQueryJUnitTestSuite line 114: Can not issue 
> executeUpdate() for SELECTs.
> Consequently, I end up in the catch block where the current transaction 
> is rolled back.
>  
> Chapter 7.9.1 of the JPA specification says:
> "After the JTA transaction has completed (either by transaction commit 
> or rollback), The container
> closes the entity manager by calling EntityManager.close."
>  
> Apparently, this is what the JPA container in NetWeaver does. With the 
> closed entity manager, however, query2 becomes unusable.
>  
> In my opinion, it's an error of the test rather than of the JPA 
> container, but I might be wrong. What do you think?
>  
> Thanks and best regards,
> Sabine
>  
> *Sabine Heider
> **SAP AG
> 
> *Pflichtangaben/Mandatory Disclosure Statements:
> _http://www.sap.com/company/legal/impressum.epx_
>  
>  
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

Re: [eclipselink-dev] 267862-EclipseLink-does-not-update-Version-of-parent-when-owned-relationship-changes

gordon.yorke@xxxxxxx (Gordon Yorke) — Wed, 25 Nov 2009 21:11:40 GMT

Updated test case to support running on server. Server apparently is configured to use a Transactional Entity Manager instead of an Extended Entity Manager. --Gordon

Gordon Yorke wrote:

Checked in
Reviewed by Andrei Ilitchev and James Sutherland

Gordon Yorke wrote:

Proposed Patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=267862
Any feedback welcome.
--Gordon
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

Re: [eclipselink-dev] Bug 296184 - JPA 2.0: Derby rounds floats when binding multiplication argument

gordon.yorke@xxxxxxx (Gordon Yorke) — Wed, 25 Nov 2009 20:53:58 GMT

Patch checked in
Reviewed by Tom Ware

Gordon Yorke wrote:

Proposed patch available
https://bugs.eclipse.org/bugs/show_bug.cgi?id=296184
--Gordon
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev