Testing a bit more I was able to successfully deploy a different web service to a different location on the same Tomcat installation. Then I copied all the resources to a new project (in Eclipse), which I deployed to a new web-app and things seem to work there. So, at least I have the problem limited down now to the original service that I wanted to deploy. Still, it's puzzling...
In the process, I happened to notice that the SOAPMonitor tool can only be used, if Tomcat is installed on port 8080. Is there a way to change the port to 80? It reverts back to 8080, even if I call the SOAPMonitor with http://localhost/.... Cheers, Martin > Dear all, > I have run into a very odd problem trying to deploy my web service > using AdminClient. I create my wsdl and wsdd files without any > problems. I also don't get any errors when I deploy the service using: > "java -cp %AXISCLASSPATH% > org.apache.axis.client.AdminClient -l http://localhost/<myURL> > deploy.wsdd" > However, the service then simply isn't there. It doesn't show up in > the list of services (only AdminService and Version do). > This is even > more awkward, since it was working fine this morning. I had the > service running, went for lunch, and it > somehow undeployed itself in the meantime. So, I tried to redeploy, > but without any success so far. Any idea what the problem might be? > Cheers, > Martin -- ---------------------------------------------------------- Martin Wunderlich, M.A. Translation/Localisation EN <-> DE www.martinwunderlich.com ---------------------------------------------------------- Free / open-source software for translation/localisation: www.martinwunderlich.com/foss-links.html ---------------------------------------------------------- Random aphorism: "Todas las cosas tienen su misterio, y la poesía es el misterio que tienen todas la cosas." "All things have their secret. And poetry is the secret that all things have." - Federico García Lorca ----------------------------------------------------------
