JB4 Management Client Required JARs
I have developed a JSR77 Management client application which I have been using with JBoss-3.0 without any problem.
I have now installed Jboss-4 DR2 and anm trying to get my application to interact with the MEJB with varying success.
What I'm after is a clear statement of which JARs are required to get a management client application to connect and interact with the MEJB.
I am using the standard jboss installation and default settings, I've tried various combinations of jars with varying results.
I'm currently using the following jb4 jars in the client app classpath:
lib/xercesImpl
lib/dom4j
lib/jboss-jmx
lib/jboss-system
lib/jboss-remoting
client/jboss-all-client
client/jboss-j2ee
client/jboss-jsr77-client
client/log4j
client/jnet
Which results in the initialContext lookup of the MEJB throwing an exception preceeded by a bunch of statements :
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TransactionManagerService
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.remoting:service=InterceptorAdapter
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TxLogger
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=XidFactory
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TxLogger
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TransactionManagerService
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.jca:service=CachedConnectionManager
ERROR [main] (ServiceMBeanSupport.java:240) - Starting failed: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
FATAL [main] (ClientServiceMBeanSupport.java:76) - Could not set up mbean server or mbeans in client
MBeanException: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
Cause: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:103)........and so on
when I have passed in the usual initialcontext :
Hashtable table = new Hashtable();
table.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
table.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
table.put("java.naming.provider.url","localhost");
ctx = new InitialContext(table);
Any ideas?
