Standalone client lookup for JBOSS JNDI

[tsg26]

Hello,

IS it true to say that , to be able to compile and run a standalone client looking up a JBOSS JNDI , one need to include all the jar file under default jboss client lib path as well as default lib path?

Base my last experience it seems to tell me unless I include what has been stated above, otherwise the standalone client would not be able to look up jboss JNP JNDI.

Eventhough thing turn out to what has been stated and done, I could not understand the following error message warning by JBOSS

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

Any helpers please?

Thanks

[barryburd]

I'm having the same problem. Did you find a way to correct this problem?

[jonlee]

Usually, all that you require for a standalone client is the jbossall-client.jar. This contains most of the normal classes to perform the JNDI lookups as well as handle the EJB interfaces. Many of the other libraries are class subset variations of jbossall-client.jar.

Some more information on how you are connecting as well as the JBoss version you are using would help. Post some code fragments on your client.