|
Ahhhh. SAAJ is a Java standard. Java standards are
different from Web services standards. To a large degree, Sun controls the Java
standards. Sun has an investment in both SOAP and ebXML, so Sun would obviously
want to promote MIME attachments via Java standards. Let me explain
further...
SAAJ provides a low-level API for Java for two
different SOAP specifications: SOAP 1.1 and SOAP with Attachments
(SwA).
SOAP 1.1 is indisputably a defacto
standard. But SOAP 1.1 doesn't define a mechanism to send attachments.
There currently is no industry consensus on the best way to send attachments.
SwA extends SOAP 1.1 to add support for MIME
attachments. SwA is the basis for the ebXML Message Service (ebMS), but it has
not gained universal adoption among the SOAP 1.1 community. In particular,
Microsoft doesn't support SwA. IBM and Microsoft released a competing
specification called WS-Attachments, which uses DIME rather than MIME. The
W3C XMLP working group basically punted on this decision in the SOAP 1.2
spec. They defined a SOAP Attachment Feature, which can support multiple
attachment mechanisms, including MIME, DIME, and base64 encoding, among others.
What this means is that we still won't have a definitive standard for
attachments in SOAP 1.2 -- but at least you have a standard mechanism to
identify which mechanism you are using.
Anne
----- Original Message -----
Sent: Tuesday, July 29, 2003 11:16
AM
Subject: Re: help needed
Thanks Anne,
You are right on the fact that more time is spent on
ironing out interop issues than building a service itself.
As per yr statement below, if SAAJ ain't yet a de
facto standard, why has it (JAX-RPC) become a part of J2EE 1.4 (java WSDP) ?
I'm a bit confused now..
Regards,
Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
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
----- Original Message -----
Sent: Monday, July 28, 2003 12:11
PM
Subject: Re: help needed
Thanks Anne. Are you aware of any interop issues
with regards to SAAJ ? Most of the examples/code I've seen so
far, are proverbial and don't exhibit true nature of SAAJ.
Has anyone (or have you) experienced any
problem/issue sending a SOAP msg with attachment( a single or multiple
attachments) to endPoint that is a non-java implementation ? Is WSDL
support ingrained with SAAJ implementation ?
Anne
Thomas Manes <[EMAIL PROTECTED]> wrote:
I recommend SAAJ (a standard API) over
Apache SOAP (an old proprietary API). Apache Axis implements
the SAAJ API.
Anne
----- Original Message -----
Sent: Monday, July 28, 2003 11:14
AM
Subject: Re: help needed
Does Apache SOAP 2.2 support SOAP attachments
over asynchronous transport ? If so, which is a better choice,
SAAJ or Apache SOAP ?
Thanks,
Scott Nichol <[EMAIL PROTECTED]>
wrote:
These
are used to support SOAP Attachments.
Scott Nichol
Do
not send e-mail directly to this e-mail address,
because it is
filtered to accept only mail from
specific mail
lists.
----- Original Message -----
From: "Kamran Ghani"
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent:
Friday, July 25, 2003 2:22 PM
Subject: help
needed
> Hi
> Why do we need JAF and Java mail
with Apache...
> kg
>
>
>
>
--------------------------------------------------------------------------------
>
Protect your PC - Click here for McAfee.com VirusScan
Online
Do you Yahoo!?
Yahoo!
SiteBuilder - Free, easy-to-use web site design
software
Do you Yahoo!?
Yahoo!
SiteBuilder - Free, easy-to-use web site design
software
Do you Yahoo!?
Yahoo!
SiteBuilder - Free, easy-to-use web site design
software
|
