|well, it seems to me that there is always going to be a spine classloader,
|and for each application an application classloader. Now if an ear or
|other "application" say includes some sars, do they get loaded with the
|system classloader or the application classloader? I'd tend to think the
|application classloader.
that is not how parent delegation works. If you put the classes in the
parent (system) those are going to be picked up. If you want to override
this then we need unification of Scoped and URL classloaders.
|I haven't had a chance to really investigate, is there a fundamental
|difference between your new classloader scheme and the scoped classloader?
|Can we unify them at some point?
Scoped class loader is more advanced than the URLCL and deals specifically
with
1- scope which could be interesting in the case of system (versions)
2- redeployment of the applications which doesnot apply to the Mbeans.
I have separated MBeanCL and URL CL as this goes deeper in the case of the
system itself, that is the about the only point that is a bit more advanced.
Unification when needed, not now afaics
marcf
|
|david jencks
|
|
|<snip>
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
