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 Dave Wolf <da...@getpersonified.com> on 2002/10/16 16:22:50 UTC
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
RE: Is there a 'thinner' client runtime?
Posted by Dave Wolf <da...@getpersonified.com>.
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:ulrich.winter@gmx.de]
> Sent: Wednesday, October 16, 2002 11:10 AM
> To: axis-user@xml.apache.org
> 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" <da...@getpersonified.com>
> To: <ax...@xml.apache.org>
> 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
> >
> >
> >
> >
>
Re: Is there a 'thinner' client runtime?
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Dave Wolf" <da...@getpersonified.com>
To: <ax...@xml.apache.org>
Sent: Wednesday, October 16, 2002 10:28 AM
Subject: RE: Is there a 'thinner' client runtime?
> Thanks Steve,
>
> What build can I pickup that would include this fix?
>
> /davewolf
you probably have to build it yourself
RE: Is there a 'thinner' client runtime?
Posted by Dave Wolf <da...@getpersonified.com>.
Thanks Steve,
What build can I pickup that would include this fix?
/davewolf
> -----Original Message-----
> From: Steve Loughran [mailto:steve_l@iseran.com]
> Sent: Wednesday, October 16, 2002 1:09 PM
> To: axis-user@xml.apache.org
> Subject: Re: Is there a 'thinner' client runtime?
>
>
> it turned out that 1.0 still needed servlet.jar client side *if* the
> client
> is java1.4, but not on previous versions. That is now fixed in CVS.
You
> dont
> need j2ee.
>
> ----- Original Message -----
> From: "Dave Wolf" <da...@getpersonified.com>
> To: <ax...@xml.apache.org>
> Sent: Wednesday, October 16, 2002 8:45 AM
> Subject: RE: Is there a 'thinner' client runtime?
>
>
>
> All I do is
>
> Service service = new Service();
>
>
> Here is the stack:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/servlet/ServletContext
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:1613)
> at java.lang.Class.getMethod0(Class.java:1732)
> at java.lang.Class.getDeclaredMethod(Class.java:1219)
> at
>
>
Re: Is there a 'thinner' client runtime?
Posted by Steve Loughran <st...@iseran.com>.
it turned out that 1.0 still needed servlet.jar client side *if* the client
is java1.4, but not on previous versions. That is now fixed in CVS. You dont
need j2ee.
----- Original Message -----
From: "Dave Wolf" <da...@getpersonified.com>
To: <ax...@xml.apache.org>
Sent: Wednesday, October 16, 2002 8:45 AM
Subject: RE: Is there a 'thinner' client runtime?
All I do is
Service service = new Service();
Here is the stack:
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/servlet/ServletContext
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:1613)
at java.lang.Class.getMethod0(Class.java:1732)
at java.lang.Class.getDeclaredMethod(Class.java:1219)
at
RE: Is there a 'thinner' client runtime?
Posted by Dave Wolf <da...@getpersonified.com>.
All I do is
Service service = new Service();
Here is the stack:
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/servlet/ServletContext
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:1613)
at java.lang.Class.getMethod0(Class.java:1732)
at java.lang.Class.getDeclaredMethod(Class.java:1219)
at
org.apache.commons.discovery.tools.ClassUtils.findPublicStaticMethod(Cla
ssUtils.java:112)
at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactor
y(EngineConfigurationFactoryFinder.ja
va:214)
at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.access$30
0(EngineConfigurationFactoryFinder.ja
va:92)
at
org.apache.axis.configuration.EngineConfigurationFactoryFinder$1.run(Eng
ineConfigurationFactoryFinder.java:17
9)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactor
y(EngineConfigurationFactoryFinder.ja
va:148)
at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactor
y(EngineConfigurationFactoryFinder.ja
va:204)
at org.apache.axis.client.Service.<init>(Service.java:111)
/davewolf
> -----Original Message-----
> From: Daniel Hägg [mailto:daniel.hagg@factum.se]
> Sent: Wednesday, October 16, 2002 11:43 AM
> To: axis-user@xml.apache.org
> Subject: Re: Is there a 'thinner' client runtime?
>
> Dave Wolf wrote:
>
> >It appears they tried to fix it as
> >
> >Bug #13149 - Client requires servlet.jar
> >
> >I'm not sure if this hit the 1.0 release?
> >
> >/davewolf
> >
> I don't have j2ee.jar on my machine and I have sucessfully created two
> clients using Axis 1.0 RC2. However, I am working with a fixed WSDL
(no
> dynamic discovery).
>
> /
> / Daniel
>
>
Re: Is there a 'thinner' client runtime?
Posted by Daniel Hägg <da...@factum.se>.
Dave Wolf wrote:
>It appears they tried to fix it as
>
>Bug #13149 - Client requires servlet.jar
>
>I'm not sure if this hit the 1.0 release?
>
>/davewolf
>
I don't have j2ee.jar on my machine and I have sucessfully created two
clients using Axis 1.0 RC2. However, I am working with a fixed WSDL (no
dynamic discovery).
/
/ Daniel
RE: Is there a 'thinner' client runtime?
Posted by Dave Wolf <da...@getpersonified.com>.
It appears they tried to fix it as
Bug #13149 - Client requires servlet.jar
I'm not sure if this hit the 1.0 release?
/davewolf
> -----Original Message-----
> From: Ulrich Winter [mailto:ulrich.winter@gmx.de]
> Sent: Wednesday, October 16, 2002 11:10 AM
> To: axis-user@xml.apache.org
> 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" <da...@getpersonified.com>
> To: <ax...@xml.apache.org>
> 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
> >
> >
> >
> >
>
Re: Is there a 'thinner' client runtime?
Posted by Ulrich Winter <ul...@gmx.de>.
j2ee.jar shouldn't be needed.
Did you try it without that?
Uli
----- Original Message -----
From: "Dave Wolf" <da...@getpersonified.com>
To: <ax...@xml.apache.org>
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
>
>
>
>
Re: Is there a 'thinner' client runtime?
Posted by Steve Loughran <st...@iseran.com>.
Its been discussed, but the notion of client runtime versus server runtime
will (apparently) go away once support for callbacks somehow gets into the
system, be it Soap over SMTP, BEEP or some other trick.
That said, if you can provide a build.xml to create an axis-applet-client
jar containing only the bits that *Everyone* agrees an applet needs, then
I'm sure that even it doesnt go into axis, we can always point to the build
file in the docs and say 'here is how to build a lightweight client'. The
nice side to that approach is that we dont need one 'axis client' jar;
everyone can build up their own with their own options in the jar.
----- Original Message -----
From: "Ben Souther" <bs...@fwdco.com>
To: <ax...@xml.apache.org>
Sent: Wednesday, October 16, 2002 8:33 AM
Subject: Re: Is there a 'thinner' client runtime?
It would be nice to see the client and server broken down into separate jar
files. I'm calling webservices from within applets.
This particular app is on an extranet so the large download and the policy
files for breaking out of the sandbox are not too much of an inconvenience
but a smaller, sandbox ready client would be a welcome site.
Re: Is there a 'thinner' client runtime?
Posted by Ben Souther <bs...@fwdco.com>.
It would be nice to see the client and server broken down into separate jar
files. I'm calling webservices from within applets.
This particular app is on an extranet so the large download and the policy
files for breaking out of the sandbox are not too much of an inconvenience
but a smaller, sandbox ready client would be a welcome site.
On Wednesday 16 October 2002 02:22 pm, Dave Wolf wrote:
> 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