obtaining MBeanServerConnection - classloading issues

[akostadinov]

Not sure I'm writing to the right place but anyways,

I want to obtain a MBeanServerConnection in an ant task to a remote jboss server.

My code is like:

ctx=new InitialContext(properties);
Object connection = ctx.lookup("jmx/rmi/RMIAdaptor");

When I run it putting jbossall-client.jar in classpath on jvm startup, then everything works fine. When I don't but instead tell apache-ant's "taskdef" task to include it in the new task's classpath (which IMO is the normal way to do it) then upon connection an exception is thrown:

javax.naming.NoInitialContextException: Cannot
instantiate class: org.jboss.naming.NamingContextFactory [Root exception is jav
a.lang.ClassNotFoundException: org.jboss.naming.NamingContextFactory]

Now can I do something to make it work? I'm not referencing org.jboss.naming.NamingContextFactory in my code so it is used under the hood for whatever reasons. It is not the only such class. Can the thing trying to load that class, be instructed to regard the classloader created by apache-ant?

No secret, ant tasks are server:start/stop/config and my code is in jboss-server-manager.

[shelly.mcgowan]

Looks like we both encountered the same problem. I ran into this when implementing the change requested in JBASM-12. Initially planned to look up the Context.PROVIDER_URL to determine the URL to use for shutdown but chose an alternative due to this error. I took the easy way out but am interested to know if it is possible.

[akostadinov]

I found http://java.sun.com/products/jndi/tutorial/beyond/misc/classloader.html.

I will try with Thread.setContextClassLoader() although that could have unexpected side effects if different tasks set it

[akostadinov]

I find somebody was in the same situation and resolved his problem that way
http://markmail.org/message/3n2fecjrxivl2yjo

Actually seems like apache-ant's junit task in 1.7.x is using the same and there are plans for more tasks to support it.
http://www.docjar.com/html/api/org/apache/tools/ant/taskdefs/optional/junit/JUnitTask.java.html

I will need to dig deeper into it to see what would be the "correct" way for implementing it...[/url]

[akostadinov]

They don't seem to be doing too much magic. Just set as a loader what loaded the JUnitTask and add additional path as specified by the user.

But I have another problem in jboss-test... Anyways things are now pretty clear. I'll start another thread in the internal testing forum once I do some testing.