Hi Srinath and folks,
|I mean as NEXT is "http://www.w3.org/2003/05/soap-envelope/role/next";
|the role given in SOAP Spec.
The spec says as follows;
+----------------+----------------------------------------------+
| Short-name | Description |
+================+==============================================+
|next |Each SOAP intermediary and the ultimate |
| |SOAP receiver MUST act in this role. |
+----------------+----------------------------------------------+
|none |SOAP nodes MUST NOT act in this role. |
+----------------+----------------------------------------------+
|ultimateReceiver|The ultimate receiver MUST act in this role. |
+----------------+----------------------------------------------+
i.e. "next" = "each SOAP intermediary on SOAP Message Path"
*OR* "the ultimate SOAP receiver"
| 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.
If A1 is a subset of componets as an intermediary, the next will
be either an other intermediary (containing a JAX-RPC runtime) or
the ultimate SOAP receiver.
If A1 is a subset of componets as the ultimate SOAP receiver,
the next never have a place behind A1 as a SOAP node. In this case,
I think that MU fault will be reasonable.
However, if the nole is not "next" but "ultimateReceiver", that's
more complicated problem. This thread might be closer than what you
pointed out.
--
Toshi <[EMAIL PROTECTED]>
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 2:04 PM
To: [EMAIL PROTECTED]
Subject: Re: MustUnderstand faults
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
