Yes, you can avoid AdminClient altogether. In AstroGrid, we customize the Axis web-application by imposing server-config.wsdd with services proeconfigured. (We also add custom web content to form the web-browseable UI.) We pack the customized web-application into a WAR and use that for deployment.
You can generate this server-config.wsdd by transplanting the contents of deploy.wsdd into the server-config.wsdd that comes with Axis. Generally, we put only a few, related services into each web-app. We find no major problems in running several web-apps each with an Axis servlet on the same Tomcat. Tomcat makes a reasonable job of deploying WARs. We find that it's slightly more robust to just copy the WAR into the Tomcat file-system and let Tomcat discover and deploy it. The admin web-app is not completely reliablewhen deploying WARs. Note that you can copy in the WAR while Tomcat is down and Tomcat will then find it when it starts up. If you have a Tomcat with no remote access, then the WAR is something that you can give to the Tomcat owner and say "install this". It's a standard packaging that they ought to know about. On Mon, 7 Nov 2005, Frederic Donckels wrote: > Hello, > > This is likely to be seen as a newbie question, but ... :) > > As far as I understand, the deployment of a webservice inside Axis > requires: > - a running server with the Axis engine servlet > - a call to this servlet through the AdminClient > > Am I right? > > Isn't there a way to avoid this? Assuming we have a server that > cannot be contacted for "administration purposes" like deploying a > webservice once it is started, how can we do that? We used to use > JaxRPC and this one could be configured quite easily (bundle every > config aspect in the war file at build, copy the war file, start the > server, you're done). > > Best regards > > Frederic > Guy Rixon [EMAIL PROTECTED] Institute of Astronomy Tel: +44-1223-337542 Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
