zipping Soap

Hi everyone, I am using Soap for doing RPCs in an Java-Web-Start-application. I need to transfer a log of Data and this takes a while. As far I understand the xml which soap produces is not packed in a way. Is Soap able to pack its messages which are transported? When yes what do I have to do for i

Re: zipping Soap

If you use a nightly build of SOAP, there is a setGzip method on SOAPContext that allows you to specify that the payload should be gzipped. There is also support for a deployment descriptor option to gzip the payload sent by the service. The nightly build has a gzip sample that demonstrates t

Re: Fw: Are there limitation on the size of the Envelope

Steve, When receiving the message, Apache SOAP will have, I think, 2 copies of the original message text, as well as a copy parsed into a DOM. The Java VM heap size on the server must be large enough to contain this for your largest message (or, conversely, your largest message must be able t

Re: Fw: Passing parameters in a SOAP RPC call

The relevant documentation is http://ws.apache.org/soap/docs/index.html Some Web tutorials are http://www.scottnichol.com/basicapachesoapcoding.htm http://www.javaworld.com/javaworld/jw-04-2001/jw-0427-soap.html http://www.onjava.com/pub/a/onjava/2002/02/27/tomcat.html Scott Nichol - Orig

Re: zipping Soap

Is this a standard part of SOAP ( compressing the message )? Or is this only something between Apache-SOAP client and an Apache-SOAP service? Scott Nichol wrote: If you use a nightly build of SOAP, there is a setGzip method on SOAPContext that allows you to specify that the payload should be

Java 1.4 SLOW

I am having a strange problem using 2.3.1 (or 2.2 or 2.1 for that matter).. When I run my soap client in 1.4 it is REALLY slow on the invoke call…. The same code in 1.3 takes no more than 30 secs to run a series of 20-30 calls.. In 1.4 it takes 5 minutes..   Has anyone had this problem?

Re: zipping Soap

It uses the Content-Encoding capability of HTTP. The Apache SOAP client always understands something gzipped. It will gzip a payload only when you specify with setGzip(true). The service always understands something gzipped. It will only gzip a payload if both the deployment descriptor enab

Content-Type and other MIME headers

I have been trying to find a way to store away the MimeBodyPart that is being sent by the Apache-SOAP client to the SOAP service, and comparing it with what I see is being sent on the wire via sniffer. Here are some interesting results: 1) When sending a multipart, SOAPContext.writeTo() does _

Unit testing

Currently, I use Cactus to unit test servetsl and JSPs. What's the recommended approach for unit testing SOAP services ... given that Apache-SOAP is another framework on top of servlets? -- To unsubscribe, e-mail: For additional commands, e-mail: