Hi Deepal, Thanks for your reply..Yes what you have pointed is right. Is there any ways I could remove the action from the service URL so that any action with respect to a service comes into the same message receiver..? I mean irrespective of the action(even null),all the messages should be directed to the message receiver that handles the service..? Thanks,Rahul.
--- On Fri, 12/18/09, Deepal jayasinghe <deep...@gmail.com> wrote: From: Deepal jayasinghe <deep...@gmail.com> Subject: Re: Services.xml To: axis-user@ws.apache.org Date: Friday, December 18, 2009, 6:29 AM Hi Rahul, I forgot something, if you have the operation name as part of the url then you do not need to worry too much about the SOAPAction. For example say you have a service called Foo and an operation called "xyz", then if you have the service url as follows, then Axis2 will do the right thing. http://localhost:8080/axis2/services/Foo/xyz Thanks, Deepal > Hi Deepal, > > thanks for your reply. I had a look at the dispatchers and there are 3 > among them which would do > > 1. SOAPActionBasedDispatcher - The requests would contain SOAPAction > as NULL too. How do I go about for this case > 2. AddressingBasedDispatcher - NA in this case > 3. SOAPMessageBodyBasedDispatcher - NA in this case. > > Below is my services.xml which works in this way: Am able to have any > Action mapping provided i > include that operation in the endpoint i.e normal endpoint : > http://localhost:8080/axis2/services/myService whereas to achieve the > result for any SOAPaction > http://localhost:8080/axis2/services/myService/Action > > * > <service name="myService" scope="application"> > <description> > InoutMessage receiver myservice > </description> > <module ref="module1"/> > <messageReceivers> > <messageReceiver > mep="http://www.w3.org/2004/08/wsdl/in-out"; > > class="sample.api.service.myServiceInOutMessageReceiver"/> > </messageReceivers> > > <operation name="operation1" > mep="http://www.w3.org/2004/08/wsdl/in-out"; class="sample.api.service. > myServiceInOutMessageReceiver"> > <actionMapping>Action</actionMapping> > </operation> > > </service> > * > * > *Can you please guide me as to how I can change the above to suit the > requirement..If am "Action" from the endpoint and include somewhere in > the codes,it would be great. > > Thanks, > Rahul. > > > > --- On *Fri, 12/18/09, Deepal Jayasinghe /<dee...@opensource.lk>/* wrote: > > > From: Deepal Jayasinghe <dee...@opensource.lk> > Subject: Re: Services.xml > To: axis-user@ws.apache.org > Date: Friday, December 18, 2009, 4:52 AM > > For that you need to create a dispatcher (a handler). If you are > familiar with Axis2 code base you can look at some of the default > dispatchers and modify that to suite for your requirement. In fact we > have dispatcher called SOAPActionBased dispatcher, that would be the > ideal one. > > Thanks., > Deepal > > Rahul Rulz wrote: > > Hello Axis2 Users, > > > > I have created the service from scratch and am using InOut message > > receiver for the same. I would like to call the message receiver for > > the requests which comes in with any SOAP action or null Soap > action. > > Could any one tell me the way to achieve this... > > > > Thanks, > > Rahul. > > > > > > > > > > -- > Thank you! > > > http://blogs.deepal.org > http://deepal.org > > -- Thank you! http://blogs.deepal.org http://deepal.org
