In Axis....... if you place the header in the request message and don't qualify the actor/role, then a handler will assume that it should be processed. I do not believe there is a facility for a handler to distinguish between the original headers sent by the client and headers added during processing. The benefit is that a handler can transform the headers into internal representations that are processed downstream. Also, headers can be attached to augment the message context.
if you place the header in the response message, then it will be passed to the next soap intermediary and it is clear that it should not be processed by at least the request flow handlers. /Chris On Wed, 20 Aug 2003 [EMAIL PROTECTED] wrote: > Hi Toshi > > what I mean as NEXT is "http://www.w3.org/2003/05/soap-envelope/role/next"; the > role given in SOAP Spec. > > what I mean is the Header addes by A1 has it's role as > "http://www.w3.org/2003/05/soap-envelope/role/next"; then who is going to play > the next role. > > Is it next HANDLER or next NODE... > > Thanks for your time ..(enthusiasum on the subject ..) :) > sorry for not making clear what next is .. > > regards > > Srianth > > On Tue, 19 Aug 2003 21:40:02 -0700 (PDT), Toshiyuki Kimura wrote > > Hi Srinath and folks, > > > > You might have lost "My definition" on the following message; > > <http://marc.theaimsgroup.com/?l=axis-dev&m=106117796225092&w=2> > > > > How do you define an intermediary as the NEXT ? > > The intermediary will be identified by a URI. What's happening? > > That is, all of the JAX-RPC handlers (= A1, A2, A3, ...), which > > are deployed for an endpoint, have the same URI. > > Additonaly, all of handler instances don't know the order of > > their turn on HandlerChain. A1 is the 1st, A2 is the 2nd, ... > > That's very interesting. > > > > -- > > Toshi <[EMAIL PROTECTED]> > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, August 20, 2003 11:55 AM > > To: [EMAIL PROTECTED] > > Subject: RE: MustUnderstand faults > > > > Hi Glan,Cris,Toshi and All, > > > > Am with Glan idea, That was what I want to clear in the first place. > > > > The SOAP intermediate(SOAP node) is a Axis server... not a Handler ....(I > > think the Cris make it quite clear). > > > > The SOAP spec talk about nodes ..not about handlers(i belive)... > > The processing (MU headers and headers in general) is done Node to node. > > > > > Handler is not a SOAP Node itself, so it doesn't have to do anything > > > to the headers to pass them along to the next Handler. Otherwise > > > you'd have to do MU checking/processing at EACH Handler, which would > > > be bad. > > > > Does that mean ..if the role is next in the Header that added in > > this node .. it SHOULD be processed in the NEXT node. > > > > next == NEXT NODE ??? > > > > hope am making sense .. > > thanks for your time ...I found the dicussion quite intersting > > > > regards > > > > Srinath > > > -- > Lanka Software Foundation (http://www.opensource.lk) > Promoting Open-Source Development in Sri Lanka > >
