Eddie Post wrote: > Frank, > > I am afraid I don't really follow you. > I didn't installed any war file.
I'm probably not anyone you want to listen to. I've never used Tomcat, and just started with Axis in JBoss/Jetty. However, I noticed that I would get the messages you got if I had deployed my WAR file (which is just a JAR which combines axis.jar with your application classes) and JBoss/Jetty picked it up, but I hadn't run the client-side Axis utility to deploy the actual Axis application. Your equivalent of the WAR file would be whatever you park in Tomcat's directories to get it to realize that there is a servlet application (namely Axis) there to deploy. When I deployed the WAR file by putting it in JBoss's hot-deploy directory, it noticed it and deployed Axis. However, for Axis to recognize your Axis application (except in the case of a .jws file), you have to code a deploy.wsdd (I don't think it *has* to be called that) and run org.apache.axis.AdminClient on it. This adds your application to (and I'm shaky here) some sort of server-side registry that Axis uses. Unless you do this, Axis can't associate a service name with your application, and will emit the message you describe even though it "has" your classes up there. You can find examples of this in the Axis UserGuide. I think example5 uses a deploy.wsdd.
