Community
Participate
Working Groups
We currently cache helper contexts for JBoss on the archive file name, and we also keep a map of archive file names to class loaders. During lookup, if we find an existing entry in the map for a given archive file name we compare the loaders to determine if a redeploy has occurred. This method of detecting a redeploy is not acceptable. The problem is that if the context loader is changed during application execution (which can and does happen) such that we cannot locate what we consider to be the application loader we assume redeploy and wipe the entry from the map. We need to register a listener with the JBoss MBeanServer so we can be notified of a redeploy.
Created attachment 174529 [details] Contains proposed fix for 2.2 stream
Fix checked into the 2.2 stream. Reviewed by: matt.macivor@oracle.com Tests: all unit tests pass as expected; sdo server tests all pass
Fix for bugs 320035 (SDO: JBoss redeploy scenario not handled correctly in SDOHelperContext) and 319171 (SDO: HelperContext cache should not be keyed on HelperContextMapKey) Reviewed by: matt.macivor@oracle.com Tests: all unit tests pass as expected
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink