Yes I did. And it is most definitely required. It seems the EngineConfigurationFactory loads the ServletContext via reflection.
I can see some discussions on the dev list where they acknowledge that indeed the ServletContext is loaded by the EngineConfigurationFactory. It looks like they think they fixed it but its still in GA. Try it yourself. Remove servelt.jar and j2ee.jar from your CP and try to run a client. /davewolf > -----Original Message----- > From: Ulrich Winter [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 11:10 AM > To: [EMAIL PROTECTED] > Subject: Re: Is there a 'thinner' client runtime? > > j2ee.jar shouldn't be needed. > Did you try it without that? > > Uli > > ----- Original Message ----- > From: "Dave Wolf" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 16, 2002 4:22 PM > Subject: Is there a 'thinner' client runtime? > > > > It appears that to consume a web service using Axis the client will need > > the following JAR's > > > > > > > > Axis.jar > > > > Jaxprc.jar > > > > Saaj.jar > > > > Log4j.jar > > > > Commons-logging.jar > > > > Commons-discovery.jar > > > > J2ee.jar > > > > > > > > Firstly, this is a huge runtime footprint for a client who simply wants > > to consume a web service. Secondly, of all the JAR's why is j2ee.jar > > being linked to? It appears from the stack that the Apache discovery > > classes are loading this through reflection. > > > > > > > > Is there a much more light-weight client runtime? > > > > > > > > /davewolf > > > > > > > > >
smime.p7s
Description: application/pkcs7-signature
