Axis runs in a servlet container, so it must run as a webapp. It's interface to the outside is a servlet. It is just a servlet that happens to process specially formatted post data.
If you treat Axis as a deployed servlet, that may help you integrate it more easily into your webapp. I'm sure it is a case of just running the defauylt axis war deployment and your webapp site by side. Then you will need to merge the two web.xml's. The final step would be to combine the needed resources in the WEB-INF. jars, server-config.wsdd, etc.... The path to the AxisServlet can be modified in the web.xml. Ben Tomasini On Tue, 2002-12-10 at 11:39, Swanson, Brion wrote: > I've scoured the Axis website for documentation elaborating on how to modify > the URL used when invoking AdminClient. > > It appears that Axis is intended to either contain my webapps or be > contained by my webapps. I have little problem understanding what is > necessary for Axis to contain my webapp, but I'm unclear about how the > AdminClient command line must change when all the Axis libs are contained > within my WAR and the Axis Servlet declarations and mappings have been added > to my web.xml. > > The command line to deploy my webapp within Axis is: > > java org.apache.axis.client.AdminClient -l > http://localhost:8080/axis/services/MyService mydeploy.wsdd > > but for deploying my webapp when it contains Axis I am instructed to "run > the Axis AdminClient against [my] own webapp" which suggests I should change > the -l URL, but to what? If I'm using Catalina as my container and my > webapp is deployed under $CATALINA_HOME/myapp, does the URL change to: > http://localhost:8080/myapp/services/MyService? > > Thank you for helping clarify this for me, > Brion > ---------------------------------------- > Brion Swanson > West Group > x3659 > ----------------------------------------
