You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Asankha C. Perera" <as...@wso2.com> on 2007/03/16 10:50:12 UTC
AddressingValidationHandler prevents the SynapseDispatcher from getting
the message
Hi
Why does the AddressingValidationHandler throw an ActionNotSupported
fault if a message contained addressing, but fails to dispatch using
addressing? In Synapse, we place a custom SynapseDispatcher to grab any
messages that have not been dispatched by any of the other dispatchers,
and if the AddressingBasedDispatcher fails, we know how to handle it.
Also this worked until Axis2 1.1.1, but now it is broken
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the SynapseDispatcher
from getting the message
Posted by "Asankha C. Perera" <as...@wso2.com>.
Thanks Glen
I will check this with Synapse ASAP
asankha
Glen Daniels wrote:
> All set (http://svn.apache.org/viewvc?view=rev&rev=520500). If you
> set "addressing.validateAction" to false in your favorite stacked
> context, the validation handler shouldn't give you any grief about the
> operation/service missing.
>
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-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] Re: AddressingValidationHandler prevents the
SynapseDispatcher from getting the message
Posted by Glen Daniels <gl...@thoughtcraft.com>.
All set (http://svn.apache.org/viewvc?view=rev&rev=520500). If you set
"addressing.validateAction" to false in your favorite stacked context,
the validation handler shouldn't give you any grief about the
operation/service missing.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the
SynapseDispatcher from getting the message
Posted by Glen Daniels <gl...@thoughtcraft.com>.
All set (http://svn.apache.org/viewvc?view=rev&rev=520500). If you set
"addressing.validateAction" to false in your favorite stacked context,
the validation handler shouldn't give you any grief about the
operation/service missing.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the SynapseDispatcher
from getting the message
Posted by "Asankha C. Perera" <as...@wso2.com>.
Thanks Glen / David! This would be great.. I didn't want to try to make
a fix on code that I was not familiar with..
Sorry for the delay in replying to this mail ...
reagrds
asankha
David Illsley wrote:
> Thanks Glen.
> David
>
> On 19/03/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> I'll try to get to it in the next day or so while I'm working on other
>> stuff, it's a quick fix.
>>
>> --Glen
>>
>> David Illsley wrote:
>> > I can by the end of the week but can't commit to sooner.
>> > David
>> >
>> > On 19/03/07, Paul Fremantle <pz...@gmail.com> wrote:
>> >> Glen/David
>> >>
>> >> Any chance either of you can provide a patch to support Synapse with
>> >> Option 3?
>> >>
>> >> Paul
>> >>
>> >> On 3/19/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> >> > Hi David, Asankha:
>> >> >
>> >> > David Illsley wrote:
>> >> > > There are therefore 3 routes forward I'd like you to consider
>> >> > > 1. Synapse deploys its SynapseDispatcher between the
>> >> > > AddressingBasedDispatcher and the AddressingValidationHandler
>> >> > > 2. Synapse deploys a custom module.xml which does not include the
>> >> > > AddressingValidationHandler
>> >> > > 3. We allow configuration of the AddressingValidationHandler
>> >> through a
>> >> > > parameter
>> >> >
>> >> > If we did 1, then we'd lose the ability to have Synapse co-deployed
>> >> with
>> >> > standard Axis services since Synapse would grab everything. If
>> we did
>> >> > 2, similar problems.
>> >> >
>> >> > I think 3 is the way to go. The simplest solution would be to
>> >> provide a
>> >> > property "addressing.disableActionValidation" which would let
>> Synapse
>> >> > shut off the exception throwing.
>> >> >
>> >> > --Glen
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > 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: 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
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the SynapseDispatcher from getting the message
Posted by David Illsley <da...@gmail.com>.
Thanks Glen.
David
On 19/03/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> I'll try to get to it in the next day or so while I'm working on other
> stuff, it's a quick fix.
>
> --Glen
>
> David Illsley wrote:
> > I can by the end of the week but can't commit to sooner.
> > David
> >
> > On 19/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> >> Glen/David
> >>
> >> Any chance either of you can provide a patch to support Synapse with
> >> Option 3?
> >>
> >> Paul
> >>
> >> On 3/19/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> >> > Hi David, Asankha:
> >> >
> >> > David Illsley wrote:
> >> > > There are therefore 3 routes forward I'd like you to consider
> >> > > 1. Synapse deploys its SynapseDispatcher between the
> >> > > AddressingBasedDispatcher and the AddressingValidationHandler
> >> > > 2. Synapse deploys a custom module.xml which does not include the
> >> > > AddressingValidationHandler
> >> > > 3. We allow configuration of the AddressingValidationHandler
> >> through a
> >> > > parameter
> >> >
> >> > If we did 1, then we'd lose the ability to have Synapse co-deployed
> >> with
> >> > standard Axis services since Synapse would grab everything. If we did
> >> > 2, similar problems.
> >> >
> >> > I think 3 is the way to go. The simplest solution would be to
> >> provide a
> >> > property "addressing.disableActionValidation" which would let Synapse
> >> > shut off the exception throwing.
> >> >
> >> > --Glen
> >> >
> >> > ---------------------------------------------------------------------
> >> > 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: 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
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the
SynapseDispatcher from getting the message
Posted by Glen Daniels <gl...@thoughtcraft.com>.
I'll try to get to it in the next day or so while I'm working on other
stuff, it's a quick fix.
--Glen
David Illsley wrote:
> I can by the end of the week but can't commit to sooner.
> David
>
> On 19/03/07, Paul Fremantle <pz...@gmail.com> wrote:
>> Glen/David
>>
>> Any chance either of you can provide a patch to support Synapse with
>> Option 3?
>>
>> Paul
>>
>> On 3/19/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Hi David, Asankha:
>> >
>> > David Illsley wrote:
>> > > There are therefore 3 routes forward I'd like you to consider
>> > > 1. Synapse deploys its SynapseDispatcher between the
>> > > AddressingBasedDispatcher and the AddressingValidationHandler
>> > > 2. Synapse deploys a custom module.xml which does not include the
>> > > AddressingValidationHandler
>> > > 3. We allow configuration of the AddressingValidationHandler
>> through a
>> > > parameter
>> >
>> > If we did 1, then we'd lose the ability to have Synapse co-deployed
>> with
>> > standard Axis services since Synapse would grab everything. If we did
>> > 2, similar problems.
>> >
>> > I think 3 is the way to go. The simplest solution would be to
>> provide a
>> > property "addressing.disableActionValidation" which would let Synapse
>> > shut off the exception throwing.
>> >
>> > --Glen
>> >
>> > ---------------------------------------------------------------------
>> > 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: 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
Re: [Axis2] Re: AddressingValidationHandler prevents the SynapseDispatcher from getting the message
Posted by David Illsley <da...@gmail.com>.
I can by the end of the week but can't commit to sooner.
David
On 19/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> Glen/David
>
> Any chance either of you can provide a patch to support Synapse with Option 3?
>
> Paul
>
> On 3/19/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Hi David, Asankha:
> >
> > David Illsley wrote:
> > > There are therefore 3 routes forward I'd like you to consider
> > > 1. Synapse deploys its SynapseDispatcher between the
> > > AddressingBasedDispatcher and the AddressingValidationHandler
> > > 2. Synapse deploys a custom module.xml which does not include the
> > > AddressingValidationHandler
> > > 3. We allow configuration of the AddressingValidationHandler through a
> > > parameter
> >
> > If we did 1, then we'd lose the ability to have Synapse co-deployed with
> > standard Axis services since Synapse would grab everything. If we did
> > 2, similar problems.
> >
> > I think 3 is the way to go. The simplest solution would be to provide a
> > property "addressing.disableActionValidation" which would let Synapse
> > shut off the exception throwing.
> >
> > --Glen
> >
> > ---------------------------------------------------------------------
> > 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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the SynapseDispatcher from getting the message
Posted by Paul Fremantle <pz...@gmail.com>.
Glen/David
Any chance either of you can provide a patch to support Synapse with Option 3?
Paul
On 3/19/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi David, Asankha:
>
> David Illsley wrote:
> > There are therefore 3 routes forward I'd like you to consider
> > 1. Synapse deploys its SynapseDispatcher between the
> > AddressingBasedDispatcher and the AddressingValidationHandler
> > 2. Synapse deploys a custom module.xml which does not include the
> > AddressingValidationHandler
> > 3. We allow configuration of the AddressingValidationHandler through a
> > parameter
>
> If we did 1, then we'd lose the ability to have Synapse co-deployed with
> standard Axis services since Synapse would grab everything. If we did
> 2, similar problems.
>
> I think 3 is the way to go. The simplest solution would be to provide a
> property "addressing.disableActionValidation" which would let Synapse
> shut off the exception throwing.
>
> --Glen
>
> ---------------------------------------------------------------------
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the
SynapseDispatcher from getting the message
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi David, Asankha:
David Illsley wrote:
> There are therefore 3 routes forward I'd like you to consider
> 1. Synapse deploys its SynapseDispatcher between the
> AddressingBasedDispatcher and the AddressingValidationHandler
> 2. Synapse deploys a custom module.xml which does not include the
> AddressingValidationHandler
> 3. We allow configuration of the AddressingValidationHandler through a
> parameter
If we did 1, then we'd lose the ability to have Synapse co-deployed with
standard Axis services since Synapse would grab everything. If we did
2, similar problems.
I think 3 is the way to go. The simplest solution would be to provide a
property "addressing.disableActionValidation" which would let Synapse
shut off the exception throwing.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: AddressingValidationHandler prevents the
SynapseDispatcher from getting the message
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi David, Asankha:
David Illsley wrote:
> There are therefore 3 routes forward I'd like you to consider
> 1. Synapse deploys its SynapseDispatcher between the
> AddressingBasedDispatcher and the AddressingValidationHandler
> 2. Synapse deploys a custom module.xml which does not include the
> AddressingValidationHandler
> 3. We allow configuration of the AddressingValidationHandler through a
> parameter
If we did 1, then we'd lose the ability to have Synapse co-deployed with
standard Axis services since Synapse would grab everything. If we did
2, similar problems.
I think 3 is the way to go. The simplest solution would be to provide a
property "addressing.disableActionValidation" which would let Synapse
shut off the exception throwing.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
[Axis2] Re: AddressingValidationHandler prevents the SynapseDispatcher from getting the message
Posted by David Illsley <da...@gmail.com>.
Hi Asankha,
There are a couple of reasons for this code..
1. During interoperability testing of the WS-A WSDL Binding Doc (in
the W3C), other participants indicated that they though that that
fault must be thrown if the received action is incorrect.
2. (Separately) During interoperability testing with MS endpoints, the
MS endpoint would reject a message that had an incorrect action,
whereas when the client and endpoint is axis2, everything is fine.
This left a general perception that there is an interoperability
problem between Axis2 and MS whereas the truth is the the client has
been incorrectly developed. I'd like client authors to find the
problem when working in the all Axis2 environment rather than it
appearing as a problem later on.
I suspect we could (and perhaps will) disagree on whether we should be
giving the user rope and a wobbly box to stand on to hang themselves
but my preference is not to.
I do, however, (as with the mustUnderstand case) agree that to use
Axis2 in an ESB, up-front validation may not be desirable.
There are therefore 3 routes forward I'd like you to consider
1. Synapse deploys its SynapseDispatcher between the
AddressingBasedDispatcher and the AddressingValidationHandler
2. Synapse deploys a custom module.xml which does not include the
AddressingValidationHandler
3. We allow configuration of the AddressingValidationHandler through a parameter
I'm happy with any of these, what do you think?
David
On 19/03/07, Asankha C. Perera <as...@wso2.com> wrote:
> David
>
> I assume you are familiar with this code, and I do not want to make a
> fix without knowing the reasons behind.. hope you could reply to me
> whether this is a defect, or the way it was designed. If its a defect I
> could file a JIRA and probably fix it..
>
> thanks
> asankha
>
> Asankha C. Perera wrote:
> > Hi
> >
> > Why does the AddressingValidationHandler throw an ActionNotSupported
> > fault if a message contained addressing, but fails to dispatch using
> > addressing? In Synapse, we place a custom SynapseDispatcher to grab
> > any messages that have not been dispatched by any of the other
> > dispatchers, and if the AddressingBasedDispatcher fails, we know how
> > to handle it. Also this worked until Axis2 1.1.1, but now it is broken
> >
> > asankha
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: AddressingValidationHandler prevents the SynapseDispatcher from
getting the message
Posted by "Asankha C. Perera" <as...@wso2.com>.
David
I assume you are familiar with this code, and I do not want to make a
fix without knowing the reasons behind.. hope you could reply to me
whether this is a defect, or the way it was designed. If its a defect I
could file a JIRA and probably fix it..
thanks
asankha
Asankha C. Perera wrote:
> Hi
>
> Why does the AddressingValidationHandler throw an ActionNotSupported
> fault if a message contained addressing, but fails to dispatch using
> addressing? In Synapse, we place a custom SynapseDispatcher to grab
> any messages that have not been dispatched by any of the other
> dispatchers, and if the AddressingBasedDispatcher fails, we know how
> to handle it. Also this worked until Axis2 1.1.1, but now it is broken
>
> asankha
>
> ---------------------------------------------------------------------
> 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