The project I want to use Axis contains a servlet that is currently being
deployed/installed/etc. by the usual tomcat ant tasks. (The taskdef lines
are listed below for clarity.)
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<taskdef name="undeploy"
classname="org.apache.catalina.ant.UndeployTask"/>
I notice that the axis-wsdl2java task (which is to say
org.apache.axis.wsdl.WSDL2Java) according to the documentation creates the
following for the server side:
For each binding: An implementation template class
For all services: One deploy.wsdd file with operation meta data
and One undeploy.wsdd file
The example deployment file in the axis documentation is:
<deployment xmlns="http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
<service name="MyService" provider="java:RPC">
<parameter name="className" value="samples.userguide.example3.MyService"/>
<parameter name="allowedMethods" value="*"/>
</service>
</deployment>
I assume the axis-admin ant task is making use of the .wsdd files to help it
know how to deploy and undeploy the service. What is the recommend approach
(or approaches) for an ant build that needs to deploy both traditional
servlets and axis based web services? Is there an example somewhere of such
a situation?
I assume a SOAP client whose stubs are generated by WSDL2Java and made use
of by a servlet should be deployed along with the servlet just like any
other java code. Is this assumption correct?
Thank you for your time and effort spent reading and responding to this
post.
