nonetheless, you command get got an edginess over that you
wish be delivering the following. unwell unquestionably
come further formerly again as exactly the same nearly very often inside case you shield
this increase.

New to JMS and thought I could code with just standard Java SE (for JNDI) and javax,jms (not included in SE library), I could connect to ANY JMS provider.
I have not tried IBM MQ, but I tried on OPEN JMS. The code compiles OK with just the jms1-1.jar (containing javax.jms). I use the following to pass the connection properties
…
Hashtable properties = new Hashtable();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
“org.exolab.jms.jndi.InitialContextFactory”);
properties.put(Context.PROVIDER_URL, “tcp://localhost:3035/”);
…
Looks pretty typical. Until I try to send a message to the OPEN JMS, I got javax.naming.NoInitialContextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory. It means the JMS provider cannot find the class. The problem get resolved after I add ALL the jar files from the LIB folder. It make no difference in compiling, but now I can access the JMS provider.
After seen Katrin’s response, It seems that a Java client DO need to include vendor specific jars to be able to connect to that provider, even though including those jars are the only thing a Java developer needs to do.

Anyone can confirm on with that?

It seems there is NO way to avoid it. I initial try to stay vendor neutral, but now I have to consider the specific jars.

Katrin