Community
Participate
Working Groups
We need to have JPA cache coordination tests utilizing protocols such as JMS and RMI on clustered WebLogic server environment.
Created attachment 124136 [details] JPA Cachecoordination tests for WebLogic Following two targets added to eclipselink.jpa.test/build.xml: <target name="server-start-cachecoordination"/> <target name="server-run-test-cachecoordination"/> JPA Sessionbean test model is used to test cachecoordination (using JMS or RMI) on preconfigured WebLogic (10.3) clustered environment. For JMS protocol, a JMS server configuration also required on WebLogic. Tests involve CRUD operations, and changes to entities are verified from the cache update notification.
Created attachment 124679 [details] updated patch for cachecoordination test implementation Reduced number of java files, removed hard-coded properties in java/xml files. Also, made easier to switch between JMS and RMI configuration for testing.
We know by experience that cache invalidation (to not confuse with propagation) was not tested in base TopLink 10.x. The kind of tests to have are: - check that it's only invalidated, not refresh - check that via UOW if children was invalidated but not the parent, when query via parent, the children will be refresh - JMS implementation cannot span thread, it's not EJB compliant
Created attachment 124791 [details] attachment patch created off the 'trunk' directory
Created attachment 125134 [details] combined rmi and jms configuration in single customizer class 1) more properties moved to persistence_cachecoordination.xml 2) usage of single session customizer class implemented for both JMS and RMI 3) removed temporary java files that employed in previous patch
checked in Praba's pacth for this bug on Feb 9, 2009.
Mass update to change fixed in target.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink