axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Graham" <>
Subject RE: where are handlers (sb headers) blown away?
Date Wed, 07 Feb 2001 03:18:00 GMT
I agree the wording is somewhat vague.  I interpret it the "check first"
way.  Further the information
is all available up front, and if there is a mustUnderstand problem, you
can avoid a lot of processing
(eg digital signature verification) up front.  Further, if some handlers
have hard undo semantics
(eg logger) this can be avoided entirely.


Steve Graham
(919)254-0615 (T/L 444)
<<Pithecanthropus Erectus>>
Emerging Internet Technologies

"MURRAY,BRYAN (HP-FtCollins,ex1)" <> on 02/05/2001
05:41:32 PM

Please respond to

To:   "''" <>
Subject:  RE: where are handlers (sb headers) blown away?

I interpret the quoted section from the SOAP spec to mean that if you do
come accross an element in the SOAP header containing the mustUnderstand
attribute you must be able to process that element sometime during the
message processing, not that it necessarily needs to be itemized before
proceeding to the processing of all message elements. Section 2 doesn't
enough detail to indicate the order of processing between header elements
and body elements, much less mandatory header elements relative to other
header and body elements.

Bryan Murray

-----Original Message-----
From: Steve Graham []
Sent: Saturday, February 03, 2001 5:30 PM
Subject: Re: where are handlers (sb headers) blown away?

Section 2 of the soap spec indicates that:

"Verify that all mandatory parts identified in step 1 are supported by the
application for this
message (see section 4.2.3) and process them accordingly. If this is not
the case then discard the
message (see section 4.4)."

It seems to me that the mustUnderstand checking must happen up front in
order to
remain compliant with soap spec.  Don't you agree?


View raw message