Thankyou all - between all these comments I managed to get it worked out :)


On Fri, 15 Oct 2004 09:02:01 -0700, Dan Ciarniello
<[EMAIL PROTECTED]> wrote:
> Pat Allan wrote:
> 
> >Do I need the Axis servlet? I assumed it wasn't necessary.
> >
> >
> Yes, you do need the Axis servlet.
> 
> >I didn't have a web.xml file, so I copied the one in the axis webapp,
> >and have the following as my only servlet and servlet mapping nodes
> >(and kept the mime mappings, etc):
> >
> ><servlet>
> >    <servlet-name>TaskWS</servlet-name>
> >    <display-name>Task Web Services</display-name>
> >    <servlet-class>
> >        com.freelancingGods.life.lifeCore.TaskWS
> >    </servlet-class>
> >  </servlet>
> >
> >  <servlet-mapping>
> >    <servlet-name>TaskWS</servlet-name>
> >    <url-pattern>/taskServices/*</url-pattern>
> >  </servlet-mapping>
> >
> >
> The web.xml from the axis webapp is sufficient for your own
> application.  Note that the web.xml is not used for configuring your web
> service; it is used for configuring Axis.  You then need to tell Axis
> about your web service which you do with
> org.apache.axis.client.AdminClient and the WSDD (Web Services Deployment
> Descriptor) that describes your service (this is where you specify your
> service class).  When you run the AdminClient, server-config.wsdd is
> created (or modified) in WEB-INF.  That file contains the description of
> your service that AxisServlet uses to process requests (including
> auto-generating the WSDL).  Check the User Guide and reference docs for
> information on using the AdminClient and WSDD.
> 
> Hope this helps,
> Dan.
> 
> 
>

Reply via email to