Apache AXIS server-config.wsdd.

[Chase Bonham]

So I want to use my web service automatically without having to explicitly run an
Admin tool to deploy it to Axis. The integration guide that comes with Axis
says that by default the engine looks for a

WEB-INF/server-config.wsdd file.

I put my service definition in there. Deployed it in my app server (Resin 3.x) and I get a SOAP service not found.


Does this mean that in order to use an Apache Axis SOAP webservice you have to use their command line tool AdminClient to deploy services?

How are folks using this in a clustered production environment of say 10 appservers? Are they running the command line tool on each app server in order to deploy?

Am I missing something here? There has to be a way to "auto" discover
webservices in Axis.


What gives?
[ April 11, 2007: Message edited by: Chase Bonham ]

[Ulf Dittmer]

In Axis 1.x there's no way to auto-discover it during runtime. Deploying means indeed running the tool. But there's an Ant task that can do this. Its invocation would look something like this:

  <target name="deploy" depends="jar">
<copy file="${jarFile}" todir="${axisLibDir}"/>
 
<java fork="true" classname="org.apache.axis.client.AdminClient">
<classpath refid="basic.class.path" />
<arg value="${srcDir}/${pkgFib}/${package.ws}/deploy.wsdd"/>
</java>
  </target>

Axis 2 makes this easier - it auto-discovers .aar files dropped into the services directory. But you can't update services this way - changes will be recognized only after the Axis web app is restarted.