You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Paul Fremantle <pz...@gmail.com> on 2007/03/08 16:21:53 UTC
Re: [Axis2] Move nustUnderstand check into a handler
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 <gl...@thoughtcraft.com> wrote:
> 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/#relaysoapmsg).
> >
> > The right way to handle this is to identify what role the SOAP node
> > that is Axis2 is playing and do mustUnderstand checking based on that
> > model.
>
> Incidentally, per the other thread [1] I'm going to be improving this
> functionality very soon to add the capability for the engine (or
> individual services / modules) to determine which roles are in play, and
> only do the MU check on those roles.
>
> We should also make sure to only PROCESS the headers targeted at those
> roles, which will be a little more coordination work between Axis, OM,
> and the Module writers.
>
> --Glen
>
> [1]
> http://www.nabble.com/AxisEngine.checkMustUnderstand-enforcing-actor-roles--t3350540.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: [Axis2] Move nustUnderstand check into a handler
Posted by Glen Daniels <gl...@thoughtcraft.com>.
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 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 handle this is to identify what role the SOAP node
>> > that is Axis2 is playing and do mustUnderstand checking based on that
>> > model.
>>
>> Incidentally, per the other thread [1] I'm going to be improving this
>> functionality very soon to add the capability for the engine (or
>> individual services / modules) to determine which roles are in play, and
>> only do the MU check on those roles.
>>
>> We should also make sure to only PROCESS the headers targeted at those
>> roles, which will be a little more coordination work between Axis, OM,
>> and the Module writers.
>>
>> --Glen
>>
>> [1]
>> http://www.nabble.com/AxisEngine.checkMustUnderstand-enforcing-actor-roles--t3350540.html
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: [Axis2] Move nustUnderstand check into a handler
Posted by Glen Daniels <gl...@thoughtcraft.com>.
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 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 handle this is to identify what role the SOAP node
>> > that is Axis2 is playing and do mustUnderstand checking based on that
>> > model.
>>
>> Incidentally, per the other thread [1] I'm going to be improving this
>> functionality very soon to add the capability for the engine (or
>> individual services / modules) to determine which roles are in play, and
>> only do the MU check on those roles.
>>
>> We should also make sure to only PROCESS the headers targeted at those
>> roles, which will be a little more coordination work between Axis, OM,
>> and the Module writers.
>>
>> --Glen
>>
>> [1]
>> http://www.nabble.com/AxisEngine.checkMustUnderstand-enforcing-actor-roles--t3350540.html
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org