Community
Participate
Working Groups
I20060412 If a container is not referenced on the classpath, we might want to remove it from the cache. This would have the characteristic that the initializer would be called again if the container is referenced again later on (see bug 120596 comment 2 for a test case). This would also avoid leaking containers during a session (even if this leak is very rare). However some clients may rely on the fact that a container initializer is called only once per session for a given container path. So this change will have to wait post 3.2.
Created attachment 38425 [details] Regression test
Classpath container issue.
Created attachment 71859 [details] Updated regression test
*** This bug has been marked as a duplicate of bug 139446 ***
Verified (running test) for 3.4M1 using build I20070802-0800.