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 "Anecito, Anthony (HQP)" <To...@rhi.com> on 2003/02/14 19:04:27 UTC

Light Weight Client using Axis

Hi All,

Does anyone have a solution of building a Axis client without using all
those JARs? My client code got bloated 10X by including the 11 JARs (5MB)
just to talk to the Axis server. The JAR's include the JAXP distrubtion from
Sun. The JAR's total size is bigger then the JRE from Sun. I am trying to
keep the entire distribution (including JARs) light weight.

Any ideas?

Thanks
Tony

Re: Light Weight Client using Axis

Posted by Tom Myers <to...@dreamscape.com>.
Anecito, Anthony (HQP) wrote:

> Hi All,
>
> Does anyone have a solution of building a Axis client without using all
> those JARs? My client code got bloated 10X by including the 11 JARs
> (5MB) just to talk to the Axis server. The JAR's include the JAXP
> distrubtion from Sun. The JAR's total size is bigger then the JRE from
> Sun. I am trying to keep the entire distribution (including JARs) light
> weight.
>
> Any ideas?

I believe the minimal client is completely XML-unaware, doesn't even
include an HTTP library as such; you open a socket with inputstream
and outputstream, you send the header data as text, you send the XML
data as text, you receive the XML result as text, and you figure out
where in that text is the fault information or, with luck, a response.
You do need, or at least I needed,

import java.net.URL;
import java.net.Socket;
import java.io.OutputStream;
import java.io.InputStream;
import java.io.BufferedOutputStream;
import java.io.BufferedInputStream;
import java.io.StringWriter;
import java.io.InputStreamReader;
import java.io.IOException;

but that was it.

Of course, you might be losing a whole lot of flexibility; ease of
coding, ease of debugging, ease of upgrading may (or may not,
especially if your SOAP calls are basically simple) go way way down.
YMMV, or then again somebody else may respond to this by showing
that this is always a bad idea. :-)

Tom Myers



AW: Light Weight Client using Axis

Posted by Stefan Henke <st...@gmx.de>.
Hi,
I´m not sure, but I have in mind that there was a discussion about this some
time ago on this list. Maybe you can check the archives to find the answers.
As I told you above, I´m not sure. So, apologize if I´m wrong.

Stefan

-----Ursprüngliche Nachricht-----
Von: Benjamin Tomasini [mailto:btomasini@neteverything.com]
Gesendet: Freitag, 14. Februar 2003 19:09
An: axis-user@ws.apache.org
Betreff: Re: Light Weight Client using Axis


That is an interesting thought.

Perhaps there is a way to build a client-only Axis-lite?

This could be an optional, be it advanced, build target that attempts to
put only the bare minimums into a single-standalone jar.  Like a Linux
boot disk.

I would assume this would mean unjaring dependancies and repackaging.

That could be a troubleshooting nightmare, and there may be some
licensing issues with Sun in regards to redistributing their stuff in a
different form.

Ben

On Fri, 2003-02-14 at 13:04, Anecito, Anthony (HQP) wrote:
> Hi All,
>
> Does anyone have a solution of building a Axis client without using all
> those JARs? My client code got bloated 10X by including the 11 JARs (5MB)
> just to talk to the Axis server. The JAR's include the JAXP distrubtion
from
> Sun. The JAR's total size is bigger then the JRE from Sun. I am trying to
> keep the entire distribution (including JARs) light weight.
>
> Any ideas?
>
> Thanks
> Tony



Re: Light Weight Client using Axis

Posted by Michael Yuan <ju...@pancake.as.utexas.edu>.
Use kSOAP. It is less than 100 KB. :) It is not as fully featured as Axis
but it gets the job done in most cases. I have been using kSOAP to access
Axis and JWSDP servers with no problems.

kSOAP does not come with a client stub generator itself. But most IDEs
(SUNOne, WSDD) have included their own stub generators (from WSDL) for
kSOAP.

For more information, check out an article about kSOAP I published on
JavaWorld a couple of months ago.

http://www.javaworld.com/javaworld/jw-08-2002/jw-0823-wireless.html

The article is in the context of J2ME. But kSOAP works on J2SE too.

cheers
Michael
----------------------------------------------------------------------------
Read Michael Yuan's technology articles
http://www.enterprisej2me.com/articles.php
Dr. Dobbs Journal, JavaWorld, IBM developerWorks and more ...
----------------------------------------------------------------------------

On 14 Feb 2003, Benjamin Tomasini wrote:

> That is an interesting thought.
>
> Perhaps there is a way to build a client-only Axis-lite?
>
> This could be an optional, be it advanced, build target that attempts to
> put only the bare minimums into a single-standalone jar.  Like a Linux
> boot disk.
>
> I would assume this would mean unjaring dependancies and repackaging.
>
> That could be a troubleshooting nightmare, and there may be some
> licensing issues with Sun in regards to redistributing their stuff in a
> different form.
>
> Ben
>
> On Fri, 2003-02-14 at 13:04, Anecito, Anthony (HQP) wrote:
> > Hi All,
> >
> > Does anyone have a solution of building a Axis client without using all
> > those JARs? My client code got bloated 10X by including the 11 JARs (5MB)
> > just to talk to the Axis server. The JAR's include the JAXP distrubtion from
> > Sun. The JAR's total size is bigger then the JRE from Sun. I am trying to
> > keep the entire distribution (including JARs) light weight.
> >
> > Any ideas?
> >
> > Thanks
> > Tony
>
>
>


Re: Light Weight Client using Axis

Posted by Benjamin Tomasini <bt...@neteverything.com>.
That is an interesting thought.

Perhaps there is a way to build a client-only Axis-lite?

This could be an optional, be it advanced, build target that attempts to
put only the bare minimums into a single-standalone jar.  Like a Linux
boot disk.

I would assume this would mean unjaring dependancies and repackaging.

That could be a troubleshooting nightmare, and there may be some
licensing issues with Sun in regards to redistributing their stuff in a
different form.

Ben

On Fri, 2003-02-14 at 13:04, Anecito, Anthony (HQP) wrote:
> Hi All,
> 
> Does anyone have a solution of building a Axis client without using all
> those JARs? My client code got bloated 10X by including the 11 JARs (5MB)
> just to talk to the Axis server. The JAR's include the JAXP distrubtion from
> Sun. The JAR's total size is bigger then the JRE from Sun. I am trying to
> keep the entire distribution (including JARs) light weight.
> 
> Any ideas?
> 
> Thanks
> Tony



Some help with the usage and notion of FAULT messages!

Posted by Apostolopoulos Paris <pa...@freemail.gr>.
Hi!
 
User status : AXIS newbie
 
Well I am developing some 'simple' web services as part of my final year
project! I am using a 100% RPC approach! I have a service that is
responsible of making some sort of user validation. The client invokes
the Logging service passing a username and password. The service checks
its credentials and if the processing is succesful returns an encrypted
string that is going to be used for the invocation of other
services,like a passport lets say :) . Ok.. my newbie question is ,
alright and what if the credentials are bad..and the logging is non
valid. Is it my responsibility  as a developer that should take care of
it, I mean that I should return a string saying 'ERROR' and the client
side.(which is implemented by me) should have the code to check the
string , or SHOULD i sent a FAULT response. From what i have red till
now, a FAULT message is only associated with exception occuring at the
AXIS engine as overal? Can i use FAULT messages to deliver businees
logic to my client? or the FAULT messages are only for technical
problems in the request/response flow! 
 
If yes, how can i send as a response a FAULT message ? through a handler
i suppose in the response flow?
 
Thank you for your time
A.P
 

RE: Light Weight Client using Axis

Posted by Anne Thomas Manes <an...@manes.net>.
Light Weight Client using AxisIn addition to kSOAP, you might also look at
Wingfoot SOAP -- www.wingfoot.com.
  -----Original Message-----
  From: Anecito, Anthony (HQP) [mailto:Tony.Anecito@rhi.com]
  Sent: Friday, February 14, 2003 1:04 PM
  To: 'axis-user@ws.apache.org'
  Subject: Light Weight Client using Axis


  Hi All,

  Does anyone have a solution of building a Axis client without using all
those JARs? My client code got bloated 10X by including the 11 JARs (5MB)
just to talk to the Axis server. The JAR's include the JAXP distrubtion from
Sun. The JAR's total size is bigger then the JRE from Sun. I am trying to
keep the entire distribution (including JARs) light weight.

  Any ideas?

  Thanks
  Tony