"david.lloyd(a)jboss.com" wrote :
| I don't really understand the hairy details behind some of the classloader
problems, but surely they could be worked around by imposing some reliance on the
dependency system for them as well?
|
If all the deployments specified their classloading dependencies
(osgi style) the problem would go away.
This also means automagically adding javaee (and the relevant container)
classloading dependencies into ejb/war deployments etc.
since we can't expect users to do this for themselves.
It's doable, but I doubt it is going to happen soon?
Another side affect of this, is that those deployments that
explictly list their package exports wouldn't have to go through the
scan of the filesystem/jars to determine what packages they export.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131493#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...