Re: [jboss-dev] JMX stuff WAS Re: M2 planning and timeline
On Fri, 2010-01-15 at 17:19 +0100, Ales Justin wrote:
> I've fixed the classloader problem.
Hard work I see, moving one code line 3 lines up. :-)
Yeh, but then I had to release it, do a clean build of the AS,
run the smoke tests (twice - once for each mbeanserver impl)
and then check the remote jmx tests had all been fixed.
That'll learn me to do it properly in the first place. ;-)
-------------------------------------------------
Modified:
projects/jbossmx/trunk/mbeanserver/src/main/org/jboss/jmx/mbeanserver/JBossMBeanServer.java
===================================================================
---
projects/jbossmx/trunk/mbeanserver/src/main/org/jboss/jmx/mbeanserver/JBossMBeanServer.java
2010-01-15 14:02:43 UTC (rev 99475)
+++
projects/jbossmx/trunk/mbeanserver/src/main/org/jboss/jmx/mbeanserver/JBossMBeanServer.java
2010-01-15 14:05:27 UTC (rev 99476)
@@ -334,10 +334,10 @@
NotCompliantMBeanException,
InstanceNotFoundException
{
- RegistryEntry previous = checkCurrent(name, null);
+ ClassLoader cl = getOuter().getClassLoader(loaderName);
+ RegistryEntry previous = checkCurrent(name, cl);
try
{
- ClassLoader cl = getOuter().getClassLoader(loaderName);
ClassLoader previousCl = null;
ps: nice catch
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx