Currently the WSDL specification does not have any way of defining headers
so this doesn't work as simply as you describe. Work is on going in this
area so this will change when the spec is revised.
For now, WSIF defines a context message associated with a WSIFOperation
which can be used for setti
Based on a quick reading of the SOAP 1.2 specs, it appears that in WSDL, the
abstract contains parts, some of which in the 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 , and process
