Originally posted by Pradeep Bhat: How does JAXM fit into J2EE web services?
JAXM is one of the JAX pack (most of them are now J2EE 1.4) that enables doc-style web services. It is asynchronous in nature, and usually relies on the underlying middleware such as JMS that supports JAXM, ebXML, etc. Unfortunately, JAXM is not widely accepted into the world of J2EE during the J2EE 1.4 discussion. It was political because Sun is pushing JAXM for reliable messaging, but IBM/Microsoft/BEA are pushing WS-Reliability. It's just a matter of interests (conflict of interests). SAAJ, aka light-weight version of doc-style web services and subset of JAXM, is now decoupled from JAXM. It is a core part of J2EE 1.4. Having said that, who uses JAXM-based web services? Some pilots done before J2EE 1.4 is finalized use it. TCPL in Canada has implemented reliable SOAP messaging using SOAP over JMS and some JAXM. Practically, it means you specify ebXML profile in the JAXM (that comes with Sun's JWSDP), and use JAXM as doc-style web services. The underlying reference implementation will treat this as reliable SOAP messaging by re-try or re-send if the recipient fails to receive it. This is all transparent to developers.
Free chapter summary/binaries of J2EE Platform Web Services can be found at <a href="http://authors.phptr.com/lai/." target="_blank" rel="nofollow">http://authors.phptr.com/lai/.</a><br />Get your copy from <a href="http://www.amazon.com." target="_blank" rel="nofollow">www.amazon.com.</a>