"jason.greene(a)jboss.com" wrote : Doesn't this just fix visibility of the
classloader from other loaders in the repository?
|
From the perspective that a dynamic class loader should be seen as
indexed to any package, yes.
"jason.greene(a)jboss.com" wrote :
| I checked the AOP implementation, and it is currently doing the same process of
manually flushing the blacklists.
|
Ok, this looking under the covers, past the ClassLoader api was supposed to be eliminated
by the dynamic class loader notion. The dynamic url notion was not well published or
tested so I can't complain. We should have the ability to configure caching behavior
for a given deployment, but we should not have to step outside of the class loading api to
do this. At least the code doing the class loading should not. This is not to say that we
better expose the caching and indexing behavior for injection and integration with
lifecycle ops via kernel beans.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986633#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...