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:
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.
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
