|
Jan,
If you look under webapps\axis\WEB-INF\server-config.wsdd,
you will find a copy of the 'deployment descriptor' file being used by Axis.
Typically when you deploy a service using AdminClient, this is the file that
gets modified -- a new <service/> element is created within it. The wsdd
also contains deployment definitions for other artifacts such as
handlers.
The Ant script you reference appears to be capable of not only building
various artifacts needed (client stubs, etc) but also packaging the entire Axis
webapp as a war, after deploying the newly generated service. Instead of using
the server-config.wsdd within axis\WEB-INF as a base starting point, the script
gives you the option of using any wsdd as a base into which your service will be
deployed.
I guess you could also just modify the Ant script, setting the conf.src
property to your <Tomcat>\webapps\axis\WEB-INF folder, and your current
axis deployment options would be the basis of the 'packaged service' (WAR
file) created by the script. (It looks like, the other alternative is to make a
'configuration file source' folder somewhere and move copies of the various
configuration files needed (server-config.wsdd & web.xml) into
it.
PS: The script is new to me too (as is Axis, so don't bank too heavily on
my perceptions), but I plan to take a shot at using it as well shortly . Will
let you know if I run into anything interesting in the process of using the
build script.
-----Original Message-----
From: Jan Agermose [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 2:16 PM To: [EMAIL PROTECTED] Subject: Re: ant script
|
- ant script Jan Agermose
- Re: ant script Jan Agermose
- Re: ant script Jan Agermose
- Almeida, Timothy
