Hi Jeff, One variation is to build your own blat.war file that includes the axis libs, and add in the the server wsdd file with your services predeployed. I do this for our commonly deployed services. Then when I copy/build the war file I don't have to separately deploy the service.
(if that was confusing ... hand deploy everything you want deployed once using AdminClient, then save off the modified server wsdd file in WEB-INF and insure it's put in any war tree your ANT/build mechanism creates) Heitzso On Tue, 2002-06-11 at 12:39, Jeff Sparkes wrote: > I'm new to AXIS, and SOAP, so I'll probably get the terminology wrong.... > > I'd like to be able to just add my services into the axis.war file and get my service > deployed without have to somehow run the AdminClient. It seems that this happens >automatically for .jws files. Otherwise, I seem to have to edit the >server-config.wsdd > file and add my service in there. I'd rather not touch the original axis.jar file. > > If I'm missing the right way to do this, please point me in the right direction. If > there's not a mechanism for this, I'd like to propose the following: when the >AxisServlet > initializes itself, it can scan throough WEB-INF (or some other appropriate >directory) > and looks for *.wsdd files. It loads each of the WSDD files and adds them to the > server. This allows me to just add my classes and WSDD deployment descriptor into >the > axis.war file and have my services initialized at load time. >
