Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-dev] bug 336726 - Make tests of the testsuite eclipselink.jpa.wdf.test run with caching

Hi Gordon,


I’d like to bring this bug back to your attention:


some entities in the test suite eclipselink.jpa.wdf.test are annotated with @Cachable. So far, we are disabling the 2nd level cache in the testsuite as EclipseLink did not support relationships from a cachable entity to a non-cachable entity. With,


you introduced this option. I investigated whether 2nd level caching can now be activate in the WDF test suite. It turned out that the model is now accepted by EclipseLink but four bugs showed up: - eclipselink.jpa.wdf.test shows issues with remove - Removed entity obtained with getRefrence is not removed from cache - Entity not properly removed from cache


and - parameterNameMismatch if caching is enabled


Maybe the first three issue are related as they all seem to have an issue with remove (somehow).


All issues are easily reproducible with the WDF test suite if you enable caching selectively in jpa/eclipselink.jpa.wdf.test/resource/eclipselink-wdf-jpa1-model/persistence.xml (applying


(Test can be run from trunk using “ant test-wdf”).


I hope this helps,




Adrian Görler

Pflichtangaben/Mandatory Disclosure Statements:


Back to the top