• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Question on SwA and SAAJ

 
Prasad Kuppa
Ranch Hand
Posts: 151
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

What is the difference between SwA and SAAJ? Both are same? Any help on this is appreciated.

Thanks,

Prasad
 
Valentin Crettaz
Gold Digger
Sheriff
Posts: 7610
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SwA, or "SOAP Message with Attachments" is a W3C note developed by HP and Micorsoft and is available at http://www.w3.org/TR/SOAP-attachments.

SAAJ, or "SOAP with Attachments API for Java (SAAJ)" is a specific Java API developed by Sun Microsystems for dealing with attachments in SOAP messages using the Java programming language.

Bottom line: SwA is not about a specific programming language while SAAJ is Java-based.
 
Prasad Kuppa
Ranch Hand
Posts: 151
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you. But, is SAAJ Specification is derived from SwA specification?

-Prasad
[ August 31, 2005: Message edited by: Prasad Kuppa ]
 
Valentin Crettaz
Gold Digger
Sheriff
Posts: 7610
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, it isn't.

From the Chapter 3 of Java Web Services in a Nutshell:

SAAJ was originally part of the Java API for XML Messaging
(JAXM), which was developed by the JSR 67 expert group. [...] During the maintenance cycle for JSR 67, it was decided to unbundle the low-level
SOAP message creation features into a separate specification, thus creating SAAJ 1.1, leaving the higher-level features to form JAXM Version 1.1. At the same time, minor modifications were made to the API to remove a dependency that would otherwise have had the undesirable effect of making SAAJ 1.1 dependent on JAXM 1.1. The result is that it is possible to use SAAJ as a lightweight library for building and exchanging SOAP messages, without requiring the inclusion of JAXM 1.1, which provides facilities that go beyond the requirements of many web service clients. JAX-RPC, in particular, uses SAAJ to construct and decode SOAP messages, but it does not require reliable messaging and therefore is not dependent on the presence of a JAXM implementation.
 
Prasad Kuppa
Ranch Hand
Posts: 151
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you, I got it. Thanks for the link.

Prasad
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic