java:/ is the local namespace.
It can only be used within same JVM.
JmsXA is pooled, there would be little point pooling
if you then transfered stuff over the wire.
It also relies on an the App Server to control it,
read the JMS spec section 8 if you are interested.
Since JBoss is modular, you can probably create a
mini-jboss for your client with a local JmsXA
Thank you. I am a bit confused since the J2EE samples from Sun client programs start out like:
(From ConverterClient.java examples for the reference implementation)
Context myEnv = (Context)ctx.lookup("java:comp/env");
Object obj = myEnv.lookup("Counter");
Not that I have ever got those to work, the following does work however:
Object obj = ctx.lookup("Counter");
So I suppose the example is wrong?
Also the use of me calling JmsXA was just to see if I could look it up using JNDI, not to do anything with it.
The examples are for an "application client".
It's an under speced and optional part of j2ee.
Basically, it allows you to run a normal java class
with a java:comp namespace configured from a deployment
descriptor and all the j2ee classes in your classpath.
JBoss doesn't have an implementation.