This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi, I am new to web services and JAX APIs. I couldn't understand the difference between JMS and JAXM. I can see both can send XML doc as messages. Is that redundant? Please help me understand this. Thanks. Deepa
That's a good question without a correct answer. JMS and JAXM are redundant from the point of view that both are messaging APIs. But, the details support the opposite view. JMS does not define a transport protocol and thus isn't as viable for integration - JAXM uses SOAP as a transport. On the other hand, JAXM only supports point-to-point communication (which is the mostly used in EAI). In general, JMS provides more performance and flexibility while JAXM provides compatibility.
JMS provides reliable asynchronous communication between enterprise components, i.e. There are message producers generating messages, while consumers receive and process messages, asynchronously....Messages exchanged via JMS may be XML, text, bytes etc.. while JAXM is a convenient (wrappered) API that makes it easy to create and send XML messages over the Internet, without worrying about the protocol. In an nutshell: 1. JMS is used within an enterprise while JAXM is used to send messages over the internet 2. JMS supports publish/subscribe model, but not sure if JAXM can send messages to multiple recepients.. 3. JMS messages can be XML, text, byes, objects while JAXM send XML messages (only) 4. JMS provides a reliable service, i.e. guaranteed delivery, whereas when using JAXM, I think calls will fail if remote host/port is unavailable. Experts - please share if you disagree.. Rama [ March 25, 2003: Message edited by: Rama Raghavan ]