The core of Axis is the AxisServlet. It gets created and init() is called by the container. Axis uses init to load the WSDD and all that good stuff. The request is sent to the AxisServlet in the doPost() method. From there Axis inspects the soap envelope and using the configuration it pulled from the WSDD tries to map it to one of your functions in your impl class. If it can map correctly, it will then call your impl function, this is the first place your code takes over (assuming you didn't implement any handlers and such).
-----Original Message----- From: Bill Keese [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 6:33 PM To: [EMAIL PROTECTED] Subject: Re: basic question about axis I'm not sure what you are asking exactly. Tomcat routes incoming requests based on the path and extension type, as specified in web.xml. For example, any requests for jws files are routed to Axis: <servlet-mapping> <servlet-name>AxisServlet</servlet-name> <url-pattern>*.jws</url-pattern> </servlet-mapping> You can look at the web.xml in the sample app released with axis. Vikas Phonsa wrote: >Hi Everybody, > >I have a very basic question about how axis intercepts calls to the >deployed services. > >An axis based web services application is not much different than a >regular web application deployed with the war structure except that we >load a bunch of axis servlets on startup and we have a >server-config.wsdd file. > >When a request comes over http it first reaches the application server >and the server passes the request to the required application. > >So when and how does axis come into picture here (assuming that we >don't have any custom handlers and stuff )? > >What happens when the request is passed from the server to the web >application? > >Thanks > >Vikas > > > > > > > >
