JMS is just a specifcation.  The JMS API is just a bunch of interfaces and it is up to each vendor to implement them.  Therefore, although the javax.jms.XXX will be standard, you will need each vendor's specific jar files to make them work.

John Chen wrote:
I want to use JMS as the transport for Axis. I would like my client to be robust enough to handle all MOM vendors therefore I have written it based on the JMS API. However, it seems that I need all the jar files on my CLASSPATH of a particular MOM vendor in order to use my client. Is this the case?

Such as in order for me to use SonicMQ, I would need all the packages in SonicMQ to be visible on my classpath. Same if I were to use IBM MQSeries.

Thanks!!

John L. Chen
Software Engineer
SOAPtest Development
ParaSoft Corporation


--
Signature
Mitchell Horowitz
Principal Systems Engineer
Tel: 1 415 643-SONIC
Western Region Team Leader
www.sonicsoftware.com


Sonic Software


 








<<inline: logo.gif>>

Reply via email to