Community
Participate
Working Groups
>Reproduction, SQL logs and proposed fix will arrive shortly >Environment: WebLogic 10.3.3 running application managed Derby 10.5.3 client XA adapter (SE derby is OK)
>Non-regression first time test execution of JUnitCriteriaSimplTestSuite.simpleModTest()
9968934
>in txn 5531 by kyuan for Feng Yu the code was modified for Criteria server testing bug# 292160 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=5531 - the problem was than the version of WebLogic it was run on was not JPA 2.0 compatible out of the box (it should have been enabled for JPA 2.0 via an application managed EM) - as a result this test was not run until now >see http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#DI_1.1:_Alternative_3:_Application_Level_Shared_Library_-_In_Use >Line 1544 in SVN rev 5518 becomes 1801 in SVN rev 5531 - we started wrapping the getResultList with transaction code inside a try/catch
Found it: Wrong package (criteria) instead of (criteria.metamodel) - but duplicate classnames and nearly duplicate functions (off by 30 lines) This fix will likely be that the changes to one of the duplicated test suites should be copied over to the one that was missed in the 3rd party submits. org.eclipse.persistence.testing.tests.jpa.criteria.JUnitCriteriaSimpleTestSuite.simpleModTest():1796 org.eclipse.persistence.testing.tests.jpa.criteria.metamodel.JUnitCriteriaSimpleTestSuite.simpleModTest():1766 Raised bug # 321902 for an overall refactor of other suites as well.
Created attachment 175962 [details] Duplicate test classes JUnitCriteriaSimpleTestSuite must be kept in sync - simpleModTest() is merged (the rest of the file remains different)
>fixed in SVN rev# 7993 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=7993
>One of the duplicate 2 tests is still failing on server testing Passes: org.eclipse.persistence.testing.tests.jpa.criteria.JUnitCriteriaSimpleTestSuite.simpleModTest Fails: org.eclipse.persistence.testing.tests.jpa.criteria.metamodel.JUnitCriteriaSimpleTestSuite.simpleModTest Since the code is the same for both tests... >fix: it is either 1) the test framework is different between the two suites - tx/non-tx related? 2) Modelgen specific related 3) The JPA model is different for the Employee entity for example
>not currently assigned
>see possibly related bug# 320399
>I am not currently assigned this work - it can be done by any developer
Deferring
Older WLS versions.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink