Why must the axis jars go into Tomcat classpath?

[Joaquim Carvalho <jo...@dei.uc.pt>]

Hi,

Bellow is Mark solution for a problem in deploying Axis services in 
Tomcat.
IF the four jars of the axis distribution are just put in "WEB_INF/lib" 
the services don't work.
IF they go to the Tomcat Classpath everything works fine.
This I checked is the case in W2000 and in MacOSX other than Linux.

My question is: is this the way it shoud be? Shouldn't webapps be self 
suficient by putting their required classes in WEB-INF? Is this a Tomcat 
problem or an Axis problem?

Joaquim


On Friday, October 5, 2001, at 01:11 AM, Mark Young wrote:

> Don:
>  
> Thanks a million.  That hint led me to the cause of all my troubles: my 
> CLASSPATH.
>  
>  
> For anyone who is running Linux and having lots of trouble getting the 
> servlet to work, I have one word: CLASSPATH.
>  
> What I have found is that I have to have the four axis lib .jars in my 
> tomcat CLASSPATH (in tomcat.sh), and have to have my xml parser 
> (xerces.jar) in there too.
>  
>  
> Feedback to the project:  If I am right, and the CLASSPATH must be set, 
> please update the installation guide to say this.  As it was when I 
> downloaded it, it says that you don't need to mess with your 
> CLASSPATH.  Thus I spent days looking at everything else.  Turns out 
> that the only way I originally got it to work was by accidentally 
> having the axis jars in my CLASSPATH when I started tomcat. 
>  
> Regards,
>  
> Mark Young
> mark@kamiak.com
>  
>
> ----- Original Message -----
> From: Glen Daniels
> To: 'axis-user@xml.apache.org'
> Sent: Thursday, October 04, 2001 3:20 PM
> Subject: RE: Axis-Tomcat meltdown
>
> Hi Mark:
>  
> The deal with configuration is this (I'm going to be brief, I need to 
> run soon):
>  
> If there is no WEB-INF/server-config.xml, the FileProvider (a 
> ConfigurationSupplier, which is the interface through which Axis 
> configures engine instances) will automatically look in the classpath 
> for org.apache.axis.server."server-config.xml".  If you look inside 
> axis.jar, you'll notice that there is just such a file.  This is the 
> default one which will be used.  Once the engine has been loaded, it 
> will write its current config (exactly equivalent to the default one 
> the first time you run it) to WEB-INF/server-config.xml.
>  
> So to start things "fresh", just delete the WEB-INF version of the file 
> and restart your app server.
>  
> --Glen
>
> -----Original Message-----
> From: Mark Young [mailto:mark@kamiak.com]
> Sent: Thursday, October 04, 2001 4:10 AM
> To: axis-user@xml.apache.org
> Subject: Re: Axis-Tomcat meltdown
>
> I should have added that I was able to invoke services before, and now 
> none at all.  This includes the admin service that lists services, and 
> lets you deploy them.  Major bummer.  I also should have said that I am 
> running Linux.
>  
> From looking at the source code, I'm guessing that the Axis servlet 
> gets service information from WEB-INF/server-config.xml.  But I'm very 
> sure that the non-source code drops don't include this file.  So I 
> don't know if my system ever had it, or how it got there if it did have 
> it.  I copied the one over from a source code drop.  This did not seem 
> to help at all.
>  
> Can someone who understands how/where Axis keeps track of the deployed 
> services (what file it is kept in, if there is one, and how that file 
> is supposed to get created/installed) please give a short explanation?  
> Or point me to something that explains it?
>  
> BTW Joaquim, I had other problems getting the server side to work 
> before I ran into this.  Are you seeing a SOAP fault message coming 
> back with the string I mentioned?  If you're having a different problem 
> that I already solved, I'd be glad to tell you how.
>  
> Mark Young
> mark@kamiak.com
>  
>
> ----- Original Message -----
> From: Joaquim Carvalho
> To: axis-user@xml.apache.org
> Sent: Thursday, October 04, 2001 1:31 AM
> Subject: Re: Axis-Tomcat meltdown
>
> Same problem. Just installed Axis (1-Oct-2001) for the first time and 
> can't make the server side work.
>
> Client side works perfectly with other SOAP services -- very nice API.
>
> Joaquim Carvalho
> Portugal
>
> On Wednesday, October 3, 2001, at 07:12 PM, Mark Young wrote:
>
> Has anyone out there run into (and hopefully solved) this problem?  I 
> must have done something terrible to my Tomcat 3.2.2/Axis installation, 
> because now when I try to invoke any Axis service, I get a soap message 
> with a fault string: "The Axis engine couldn't find a target service to 
> invoke! ...."
>  
> I've tried many things (since I don't have a good idea about what the 
> real problem is), including replacing webapps/axis with a fresh copy of 
> the original stuff.  That didn't work.
>  
> Any clues?
>  
> Thanks,
>  
> Mark Young
>  
>