Let me try to add more insight. Dispatching has two aspects Service Dispatching Operation Dispatching
Service Dispatching is mandatory before Operation dispatching to happen which is kind of obvious. Dispatchers "do not" dispatch if dispatching has already happened. Meaning if addressing based dispatcher has dispatch the service all the preceding service dispatchers will not try to do dispatching. Service dispatching is done based on the following criteria, which are in decreasing priority WSA actction URL based namespace of the body element operation dispatching is based on following criteria which are again in the decreasing priority. WSA action soap action url base first element of the body So if you insert your own url based dispatcher before Axis2's url based dispatcher the framework will make sure that if your dispatchers manages to dispatch then not to override your dispatching. No manual removing dispatchers is necessary. There is a dispacher abstract class if i remember right.. Regards Chathura On 10/31/05, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi Wan, > I see Chinthaka has already answered this but I'll put in my comment as > well :) > See the comments inline > > On 11/1/05, Wan Luo <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I am trying to integrate Axis with an existing webapp. What I am planning > to do is remove the AxisServlet and wrapping the AxisEngine in my own > servlet. My servlet detects the web service the user is trying to hit from > the URL, so I have no need for dispatch to find the service, as I can handle > it in my own servlet. > > > > In short, I really only need to process the SOAP message and extract the > parameters. > > Your service is found based on the URL? Great because Axis already has a > URL dispatcher. You can use Axis 2 the way it is for your URL dispatching. > (I guess the need for the custom servlet was to do this special > dispatching). > The thing with the servlet is Axis servlet is somewhat complex! You'll need > to dig deep into the Axis2 concepts to write a replacement for the Axis2 > Servlet. > You can instead try a servlet filter if you need a quicker and easier way > to deal with your SOAPMessage directly. > > > The Architecture guide says that "there is a special case of using the two > way transport where the first four phases in the In-Phase most likely to do > nothing." > > > > Another option I was considering is overwriting the dispatch handler by > using a custom handler, but I have not seen any documentation on how to > override behaviour in the pre-defined phases. Any input is appreciated. > > > > > > -- > Ajith Ranabahu -- Chathura Herath http://www.bloglines.com/blog/chathurah
