New Issue from F2F: Handling badly formed SOAP Messages.

During the F2F I was actioned to raise an Issue with respect to the first
Ednote in SOAP 1.2 Part 2 section, part of the HTTP binding [1].

The ednote states:
As described this model tends to hide a malformed message from the local
SOAP Node and handle the malformation in the binding - basically because it
would not be possible to instantiate the CurrentMessage to pass up for
processing. An alternate formulation might be to allow CurrentMessage to
carry badly formed messages and let the SOAP processor/node deal with it. As
presented here we can have define the bindings behaviour with respect to
particular failures. 

The issue that the ednote raises is two fold:

1) From a descriptive point of view where do we place the responsibility to
describe behaviour associated with the receipt of poorly formed SOAP
messages? Malformations might include: XML that is not-well formed;
Unsupported envelope version; some unsupported message encapsulation (eg

2) From a more practical point-of-view, is it right that a binding
implementation 'hide' the receipt of such 'broken' messages from the SOAP
processor/node. This may be more moot, because it probably makes
inappropriate assumptions about the structure of an implementation.

The WG felt that this topic warranted further discussion.


Stuart Williams

Received on Wednesday, 6 March 2002 05:48:07 UTC