Thanks a lot for all the suggestions.
>If you really are limited to a few hundred K or >less of jar files, using JAX-RPC is going to be
>tough.
Then, I'm assuming that the current version of JAX-RPC was not designed to support light SOAP clients. I get more of the impression that JAX-RPC fits better to develop a SOAP client that runs on a J2EE server, i.e. a servlet application that consumes a web service and serves HTML to the user, rather than an applet that directly consumes the web service and displays the results. Can someeone from Sun confirm this?
>(1) Use Java Web Start.
It is an option that we are considering, but still if there would a way to not add so much to the size of the applet that would be manifold better since some clients may end up using Web Start and others may not.
>(2) Don't use JAX-RPC. For simple lightweight operations something like
>XML-RPC may be more suitable. And the jar file is less than 60K.
60K sounds very good. With a lightweight SOAP client such as XML-RPC you are mentioning, is it possible to build a SOAP client that consumes a stateful web service and maintains a session?
By the way, we will assume that the clients have JRE 1.4 at least, so they already have the XML parsers.
Regards,
Mete
---------- Original Message ----------------------------------
From: "Peter C. Tribble" <ptribble_at_hgmp.mrc.ac.uk>
Reply-To: "Peter C. Tribble" <ptribble_at_hgmp.mrc.ac.uk>
Date: Mon, 29 Sep 2003 14:19:41 +0100 (BST)
>
>>>>I went through the JWSDP 1.2 tutorial. As I looked at the ant build scripts
>used to compile the JAX-RPC client code, I realized that there were a lot of JAR
>files that were included. This worried me a little because we have to package a
>JAX-RPC client with our applet product and we cannot afford to add more than
>several 100KB's to the size of the applet. The jaxrpc-impl.jar by itself is 1.4
>MB!! Obviously there must be a lot of classes in jaxrpc-impl.jar that aren't
>necessary for the client run-time environment. It seems like that there are also
>jar files that jaxrpc-impl.jar depends on and needs.
>>>>
>>>>What are the minimum classes that are required in order to be able to run the
>JAX-RPC reference implementation client run-time environment? What is the total
>size of all these classes?
>
>If you really are limited to a few hundred K or less of jar files, using
>JAX-RPC is going to be tough.
>
>The two solutions I'm using are:
>
>(1) Use Java Web Start. This doesn't help the first time, but if you've
>got clients who use the application a lot then they'll only have to download
>it the once and it will be much quicker the next time.
>
>(2) Don't use JAX-RPC. For simple lightweight operations something like
>XML-RPC may be more suitable. And the jar file is less than 60K.
>
>-Peter Tribble
>HGMP Computing Services
>http://www.hgmp.mrc.ac.uk/~ptribble/
>
>