You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by Ulrich Winter <ul...@gmx.de> on 2002/10/10 15:48:42 UTC

why does AdminClient need the servlet API?

Hi,

My AdminClient throws a
[java] java.lang.NoClassDefFoundError: javax/servlet/ServletContext

That occurs during initialization of the engine configuration from within
org.apache.axis.configuration.EngineConfigurationFactoryFinder.

Shouldn't AdminClient be usable from within a naked j2se environment?

Bye,
Uli

Re: why does AdminClient need the servlet API?

Posted by Richard Sitze <rs...@us.ibm.com>.

This is bugzilla #13149.  I've verified that the fix IS in 1.0... so there 
is something else going on.

Would you provide a dump of everything you see on output?

Thanks, <ras>

*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development




"Ulrich Winter" <ul...@gmx.de>
10/10/2002 08:48 AM
Please respond to axis-dev
 
        To:     <ax...@xml.apache.org>
        cc: 
        Subject:        why does AdminClient need the servlet API?

 


Hi,

My AdminClient throws a
[java] java.lang.NoClassDefFoundError: javax/servlet/ServletContext

That occurs during initialization of the engine configuration from within
org.apache.axis.configuration.EngineConfigurationFactoryFinder.

Shouldn't AdminClient be usable from within a naked j2se environment?

Bye,
Uli