org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean
is the following codeblock:
// This is a fix for the SAR TCL problem in 4.0
// Allow the classloader in the value map to be an ObjectName
if (valueMap != null)
{
Object obj = valueMap.get(CLASSLOADER);
if (obj != null && obj instanceof ObjectName)
{
MBeanEntry clEntry = null;
try
{
clEntry = get((ObjectName) obj);
}
catch (InstanceNotFoundException e)
{
throw new RuntimeOperationsException(
new IllegalArgumentException(e.toString()));
}
valueMap.put(CLASSLOADER, clEntry.getResourceInstance());
}
}
What is this for? The following dispatch to the invokePreRegister is
not using the correct thread context class loader. It needs to be using
the class loader of the mbean being registered so that any scoped
classes
that are loaded as part of the registration are available. I'm
correcting
this, but I need to know what the source of this duality of type is.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
