Paul Fremantle wrote:
Cool! I'd love to implement this in Synapse too. Basically have a way
of defining the roles a Synapse node implements.
Yup - you'll just configure that in Synapse and then pass it down to Axis.
--G
Paul Fremantle wrote:
> David, Sanjiva
>
> Shouldn't we be using the SO
Cool! I'd love to implement this in Synapse too. Basically have a way
of defining the roles a Synapse node implements.
Paul
On 3/8/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Paul Fremantle wrote:
> David, Sanjiva
>
> Shouldn't we be using the SOAP role model to handle this kind of
> situation.
Paul Fremantle wrote:
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It seems to me that what you are describing is a case where
the Axis2 engine is not the ultimateReceiver (see 2.7 Relaying SOAP
Messages http://www.w3.org/TR/soap12-part1/#relaysoapms
Doh! Yep thats what I meant.
Paul
On 3/8/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Paul Fremantle wrote:
> * it must fault if there are mustUnderstand headers targeted at its roles
MU headers that it doesn't actually understand, you mean. :)
--G
Paul Fremantle wrote:
* it must fault if there are mustUnderstand headers targeted at its roles
MU headers that it doesn't actually understand, you mean. :)
--G
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
Jeremy
I think maybe you've misread the spec.
Basically the relay attribute is a red-herring in this case, because I
for one have never seen a relay header. The model is actually
reasonably simple (excluding the relay attribute for the minute):
* headers that are not explicitly marked with a rol
Hi guys ...
On 21/02/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It seems to me that what you are describing is a case where
the Axis2 engine is not the ultimateReceiver (see 2.7 Relaying SOAP
Messages
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It seems to me that what you are describing is a case where
the Axis2 engine is not the ultimateReceiver (see 2.7 Relaying SOAP
Messages http://www.w3.org/TR/soap12-part1/#relaysoapmsg).
The right way to h
Wait wait .. not yet!
David, you can just have another handler that goes before the built-in
MU handler that flags any headers you want to allow thru without causing
grief. Wouldn't that do the trick?
Sanjiva.
On Wed, 2007-02-21 at 08:31 -0500, Davanum Srinivas wrote:
> Give 'em rope :) +1
>
>
Give 'em rope :) +1
thanks
-- dims
On 2/21/07, David Illsley <[EMAIL PROTECTED]> wrote:
I'm coming back to this after focussing on other things...
I agree with everyone that mustUnderstand checking is a core, and
important (if sometimes annoying) SOAP processing rule. I also don't
advocate ANY
I'm coming back to this after focussing on other things...
I agree with everyone that mustUnderstand checking is a core, and
important (if sometimes annoying) SOAP processing rule. I also don't
advocate ANYONE deploying a SOAP web services engine that doesn't do
that checking.
That said, I'm try
Hi David,
If the mustUnderstand handler runs last, that means a node cannot ignore a
header until all the handlers have
executed. Until the handler executes, the node does not know if it must
process the header or not. One would think
that a check like mustUnderstand which is fundamental to SOAP
Hi David ;
What do you mean by adding a handler which run at last. I think that is
something we can not do b'coz after Dispatching phase its up to the sys
admin to decide the phases he want to use , according to your suggestion
we need to have a reserved phase in user phase to put that particular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
Good idea, I always consider handlers as an optional component in the
execution chain, which one can opt to keep out. And at the same time one
might try to run Axis2 engine without a single handler.
IMO, must understand thing is an absolute
Hi all,
I'm looking at using the axis2 engine as part of a larger system which
will have a set of roles which we want respected and perhaps a set of
headers whcih should be ignored for mustUnderstand checking because
anothe rpart of the system will deal with them.
Currently the mustUnderstand che
15 matches
Mail list logo
