You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Bates, Alex" <AB...@teradata-ncr.com> on 2002/11/27 23:43:33 UTC

RE: why have to copy .class files of existing webapp into Axis we b-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:steve_l@iseran.com] 
Sent: Wednesday, November 27, 2002 11:57 AM
To: axis-user@xml.apache.org
Subject: Re: why have to copy .class files of existing webapp into Axis
web-inf folder??


----- Original Message -----
From: "Alex Bates" <ab...@san.rr.com>
To: <ax...@xml.apache.org>
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.