SAAJ is just an API. Any interop issues must be
blamed on the implementation, not on the API. SAAJ is the standard low-level
SOAP API for Java. The SAAJ API gives you direct control of the SOAP
envelope constructs. Bear in mind that both JAX-RPC and JAXM use the SAAJ API
under the covers to construct and manipulate the SOAP
envelope.
SAAJ is not WSDL aware. If you want to construct
your SOAP envelope using the assistance of WSDL, you should use the JAX-RPC
API.
Plenty of people have experienced interop issues
when communicating with an endpoint developed using a different SOAP
implementation -- with or without attachments. And these difficulties arise even
among different SOAP implementations for Java. Interop is a lot better now than
it was a year ago, but you'll still encounter some difficulties when you start
using more advanced features (complex types, attachments, headers, etc.).
SAAJ is based on the SOAP with Attachments
specification, which hasn't really established itself as a defacto standard. In
particular, Microsoft .NET doesn't support SOAP with Attachments. Instead it
supports WS-Attachments, which is based on DIME rather than MIME packaging. Many
SOAP implementations for Java support both MIME and DIME attachments. The W3C
XMLP working group is developing another attachments proposal called
PASWA.
Anne
|
- help needed Kamran Ghani
- Re: help needed Scott Nichol
- Re: help needed Martin Gainty
- Re: help needed Vishal Shah
- Re: help needed Anne Thomas Manes
- Re: help needed Vishal Shah
- Re: help needed Anne Thomas Manes
- Re: help needed Vishal Shah
- Re: help needed Anne Thomas Manes
- Re: help needed Vishal Shah
- Re: help needed Vishal Shah
- Re: help needed Anne Thomas Manes
- help needed Bivins, Jeff
- Re: help needed Scott Nichol