Thanks for the reply.  I ended up having to sign a bunch of jars:
axis.jar
commons-logging.jar
commons-discovery.jar
jaxrpc.jar
saaj.jar
log4j-1.2.4.jar
 
Not the most elegant solution.  I'll check out the client you tried.
-----Original Message-----
From: Grant Echols (JanusLogix) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 23, 2002 11:36
To: [EMAIL PROTECTED]
Subject: Re: Thin client for applets?

I haven't seen anyone respond on this thread so I'll poke in.
 
I found the same problem and we really don't want to be signing applets, etc. so we found a lightweight SOAP 1.1 client on sourceforge.net - Spheon JSoap. We've found it works really well so far but I we have fairly limited needs. Check it out to see if it works for you:
 
 
Later,
 
Grant
----- Original Message -----
Sent: Monday, October 21, 2002 9:26 AM
Subject: Thin client for applets?

Is anyone working on thinning out the client code so it can be used from an applet without signing all of the jars and adding entries to java.policy?  There are a myriad of issues ranging from accessing System.getProperty to logging to getting class loaders that break using the Axis client code.  Was this use case just not in the picture when Axis was designed?

Reply via email to