I use org.apache.axis.utils.Admin and generate a new server-config.wsdd offline first (you could do edit the file manually too).. And then use that server-config.wsdd as part of my war file.. This way my services always show up registered..
-- Rajal -----Original Message----- From: Craig Lindley [mailto:[EMAIL PROTECTED] Sent: Monday, December 13, 2004 12:36 PM To: [EMAIL PROTECTED] Subject: RE: "Rooting" Axis services We deploy Axis and our webservices together in a single war and we still have the problem that if we: 1. register our webservices with Axis using the AdminClient program 2. exercise our webservices to verify they deployed correctly 3. stop tomcat and then restart our webservices are gone (meaning they must be registered). This is 100% reproducible. How do we go about getting around this? Craig Lindley On Mon, 2004-12-13 at 13:06, THOMAS, JAI [AG-Contractor/1000] wrote: > Andrew, > We are already doing that. What you need to do is, instead of deploying Axis as a separate web app, integrate Axis servlet to your war project. Then define your desired url for the Axis servlet in web.xml. > > Jai > > -----Original Message----- > From: ANDREW MICONE [mailto:[EMAIL PROTECTED] > Sent: Monday, December 13, 2004 1:56 PM > To: [EMAIL PROTECTED] > Subject: "Rooting" Axis services > > > Well, after much pain from the dubious interoperability of .NET clients and throwing a grand total of 7,091 lines of code I have my first Axis web service running in production (as well as a much greater appreciation of Bea WebLogic Integration and WebMethods). I was wondering if anyone had the magic formula with tomcat for "rooting" Axis, just for aesthetic purposes so: > > http://mydomain/axis/services/endpoint > > becomes > > http://mydomain/endpoint > > Just in case someone just had the config instructions off hand. RTFM these days seems to be an exercise of finding the needle in Google's haystack. -- Andy
