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]
