I don't
think the distinction between JAXM and SAAJ given below is exactly
correct. The documentation that ships with the JWSDP (in
jaxm-1.1.1\docs\index.html) says this.
SOAP with Attachments API for
JavaTM (SAAJ) 1.1
This specification covers the
This specification covers the
javax.xml.soap package, which provides the API for creating and
sending SOAP messages.JavaTM API for XML Messaging
(JAXM) 1.1
This specification covers the
This specification covers the
javax.xml.messaging
package, which provides the API for using a messaging provider to send
messages.Elsewhere
I've seen the distinction described by saying that SAAJ supports point-to-point
SOAP messaging while JAXM supports SOAP messaging using a provider. I'd
imagine that most implementations of JAXM would be built on top of an
implementation of SAAJ. What do I know though? I also thought the
logical way to build an implementation of JAX-RPC would be to build it on top of
an SAAJ implementation and I'm not aware of any Java-based web service toolkit
that has done that.
-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 6:55 PM
To: [EMAIL PROTECTED]
Subject: RE: What is the difference between SOAP and JAX-RPC
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 6:55 PM
To: [EMAIL PROTECTED]
Subject: RE: What is the difference between SOAP and JAX-RPC
- JAXM: an XML-oriented API that does not support WSDL and assumes that the application constructs the XML message.- SAAJ: a low-level API that lets the application work directly with the SOAP message structure.
***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************
