Hello Wes,
Why do you want to check wsa:action first? If soap action and wsa:action are both set then they must be the same, otherwise a fault should be generated. Anyway, the only way at the moment to look at the wsa:action is to engage the Addressing module. This will cause the addressing handlers to run in the PreDispatch phase. If you want the wsa:action to be checked first then you must move the SoapActionBasedDispatcher to run after this, the Dispatch phase would be a good candidate.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you find the time to do it again?
Deepal Jayasinghe <[EMAIL PROTECTED]> wrote on 12/07/2006 06:45:57:
> Hi Change you axis2.xml as follows;
>
> <phaseOrder type="inflow">
> <!-- System pre defined phases -->
> <phase name="Transport">
>
> <handler name="SOAPActionBasedDispatcher"
>
> class="org.apache.axis2.engine.SOAPActionBasedDispatcher">
> <order phase="Transport"/>
> </handler>
> </phase>
> <phase name="Security"/>
> <phase name="PreDispatch"/>
> <phase name="Dispatch"
> class="org.apache.axis2.engine.DispatchPhase">
> <handler name="AddressingBasedDispatcher"
>
> class="org.apache.axis2.engine.AddressingBasedDispatcher">
> <order phase="Dispatch"/>
> </handler>
> <handler name="RequestURIBasedDispatcher"
>
> class="org.apache.axis2.engine.RequestURIBasedDispatcher">
> <order phase="Transport"/>
> </handler>
> <handler name="SOAPMessageBodyBasedDispatcher"
>
> class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
> <order phase="Dispatch"/>
> </handler>
> <handler name="InstanceDispatcher"
> class="org.apache.axis2.engine.InstanceDispatcher">
> <order phase="Dispatch"/>
> </handler>
> </phase>
> <!-- System pre defined phases -->
> <!-- After Postdispatch phase module author or or service
> author can add any phase he want -->
> <phase name="OperationInPhase"/>
> </phaseOrder>
>
> Wes Caldwell wrote:
>
> >How do you reverse the order? Meaning, how do I make Axis look at the
> >wsa:action first, instead of the HTTP Soap action header. What specifically
> >is the change in axis2.xml?
> >
> >Thanks,
> >
> >Wes
> >
> >
> >-----Original Message-----
> >From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, July 11, 2006 10:45 AM
> >To: [email protected]
> >Subject: Re: [Axis2] WS soap action question
> >
> >Well , it is first read SOAP action , and try to dispatch using that ,
> >and next try to dispatch using wsa:action if it dose not find service
> >and operation using SOAP action .
> >
> >Any way you can change the dispatching order very easily by changing
> >axis2.xml
> >
> >Wes Caldwell wrote:
> >
> >
> >
> >>A related question. What is the order of reading in Axis 2 for the SOAP
> >>Action? Meaning, if I am using WS-Addressing, and the SOAP Action element
> >>is part of the SOAP Header, as well as the HTTP SOAP Action Header being
> >>present in the request, which is interpreted first by Axis 2?
> >>
> >>Thanks,
> >>
> >>Wes
> >>
> >>
> >>-----Original Message-----
> >>From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
> >>Sent: Thursday, June 29, 2006 7:25 AM
> >>To: [email protected]
> >>Subject: Re: [Axis2] WS soap action question
> >>
> >>Michele Mazzucco wrote:
> >>
> >>
> >>
> >>
> >>>Hi all,
> >>>
> >>>how,
> >>>
> >>>
> >>>
> >>>
> >>Read HTTP headers and SOAP Action header.
> >>
> >>
> >>
> >>
> >>
> >>>when
> >>>
> >>>
> >>>
> >>>
> >>Whenever message comes to the engine.
> >>
> >>
> >>
> >>
> >>
> >>>(and where)
> >>>
> >>>
> >>>
> >>>
> >>AxisServlet.
> >>
> >>-- Chinthaka
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
