Good news - it worked! I simply copied the servlet declarations from the Axis web.xml into my own webapp's web.xml (following its own servlet declarations), copied all the necessary Axis JARs into my lib directory, and voila.
The axis url becomes http://myserver:8080/mywebapp/services/myWebService?wsdl Also, I created a .NET client for this Axis web service (using .NET's wsdl.exe), and successfully called a method I'd exposed. One note here: the wsdl.exe has a bug in that it missed the :8080 port - so I had to edit the generated C# file to fix this. Alex -----Original Message----- From: Bates, Alex Sent: Wednesday, November 27, 2002 2:44 PM To: '[EMAIL PROTECTED]' Subject: RE: why have to copy .class files of existing webapp into Axis web-inf folder?? Thanks for the recommendations, I'm going to try to integrate Axis into my webapp. I'll post a message with the results. You might have noticed from my Microsoft reference that my transition from Wintel to Java is a recent one. Alex -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 11:57 AM To: [EMAIL PROTECTED] Subject: Re: why have to copy .class files of existing webapp into Axis web-inf folder?? ----- Original Message ----- From: "Alex Bates" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 00:41 Subject: why have to copy .class files of existing webapp into Axis web-inf folder?? > Hi, > > I have an existing webapp running on Tomcat. I want to expose some > methods in this webapp as Axis web services. Axis is a separate webapp > - the examples I've seen so far have had to copy .class or .jar files > into the Axis WEB-INF\classes directory. > > But this approach doesn't seem reasonable, it would lead to versioning > issues (i.e. how often to copy from > "tomcat\webapps\MyWebApp\WEB-INF\classes" to > "tomcat\webapps\axis\WEB-INF\classes" to keep the two versions in sync > ). > > What I'm looking for is something similar to the ability to expose > existing COM components as web services with Microsoft's WSTK; but > instead of COM components they're Java components running in a webapp. > > I tried simply creating a WSDD for my existing app and not copying the > .class and .jar files into the axis\WEB-INF directory, and got the > following exeption: separate webapps=separate classloaders; of course you got a classNotFoundException. What you need to do is add axis.jar and dependent jars to your webapp, and copy the relevant bits of axis' web.xml for it to work. Then have your adminclient talk to the new webapp, instead of axis.
