Is this the correct behaviour? Presumably, if a first header references a second header targeted at '.../none', it does depend on that second header... and hence I would expect the "SOAP Encoding processor" to deserialise both the first and the second header. Or am I misinterpreting what you were suggesting? Jean-Jacques. Shouldn't the "SOAP Encoding processor" Jacek Kopecky wrote: > I just disagree with the fact that whether or not to dereference > the href attribute in SOAP Encoded data is dependent on > application semantics. > If the application requires to be able to decide whether or not > to dereference some URI, the URI must be a value in the data > graph. IMO it's the SOAP Encoding processor that MUST handle SOAP > Encoding references. > It is true though that the data wouldn't be deserialized (and > therefore references needn't be resolved) for example on a header > targeted at '.../none'. [...]Received on Tuesday, 4 December 2001 03:34:08 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:05 GMT