i would actually recommend avoiding it - especially if you make by-hand modifications to your WEB-INF/server-config.wsdd file, which is the real authority of what's deployed to your server.
now if you're trying to deploy a new service into a server without bouncing it i don't know - you'll have to look at the source and see if there's a way to get the Axis engine to reload its config (there must be a way because the admin service does just that). then it's just a matter of getting the new classes loaded into a classloader and invoked. but if you're just talking about configuring a server while it's down WEB-INF/server-config.wsdd is your file. hth. ...............ron. > 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 >
