You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Jeff Greif <jg...@alumni.princeton.edu> on 2002/10/21 15:15:12 UTC

[WSIF] soap headers and attachments, in theory

Based on a quick reading of the SOAP 1.2 specs, it appears that in WSDL, the
abstract <message> contains parts, some of which in the <binding> may be
designated as soap headers or attachments.  Does this mean that in theory,
an Axis or WSIF client need only provide the input parts as named in the
input <message>, and process whatever output parts come back in the output
<message> without ever having to know at the client level that some of these
are transported as headers or attachments?  Is this theoretical transparency
(if I haven't misinterpreted the specs) compromised by handling of faults?

Also, what are the current limitations of the support for headers and
attachments?

Jeff