Re: [JBoss-dev] Nested JMX Service Groups...??!

[Scott M Stark]

There are two other simple approaches to getting the class loader fixed.
1. Add the jboss.jar to the classpath
2. Remove the jxmri.jar from the classpath and create a url classloader that
contains the jmxri.jar and jboss.jar and use that to load MLet, MBeanServer,
etc.

Personally I'm leaning to using the domain name as its a definative configuration
item that your likely to set anyway.

> riiiigght....
> 
> the idea of "test the domain *name*" doesn't sound soo bad after all.
> 
> The reason is that it is a simple place to define the integration (by
> scoping your domain in JBoss's).  Therefore JBoss will assume that you are
> "JBoss" aware and that your management is in place... working on String will
> for sure be safe :)
> 
> hehe, I guess the second solution will have its problems too.  That is when
> you know your codebase is too big, a simple change triggers hell
> 
> marc
> |



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development