OK, where does the following code go?
VersionSoapBindingStub binding = (VersionSoapBindingStub) new
VersionServiceLocator()
.getVersion();
// Compress the request
binding._setProperty(HTTPConstants.MC_GZIP_REQUEST, Boolean.TRUE);
// Tell the server it can compress the response
binding._setProperty(HTTPConstants.MC_ACCEPT_GZIP, Boolean.TRUE);
// invoke the service
String result = binding.getVersion();
I use WSDL2JAVA to generate my classes. Am I going to have to hand edit
one of these classes I don't normally change? Can I plug something into
wsdl2java to do that for me?
Thanks.
Davanum Srinivas wrote:
already done :)
http://wiki.apache.org/ws/FrontPage/Axis/GzipCompression
-- dims
On 5/17/06, Thom Hehl <[EMAIL PROTECTED]> wrote:
We're using Axis-java 1.3. I have a project to compress the SOAP
payload. I was thinking it would be better to compress the entire SOAP
envelope. How would I do this?
At some point, invoke is probably using java.net and sending data in and
out through some kind of input stream. I would like to have axis look at
startup for certain classes that I feed it as subclasses of
FilterInputStream and FilterOutputStream. They would wrap these around
the InputStream and OutputStream currently communicating with the
sockets. THis would allow fast cheap and easy implementation of
compression of the entire SOAP envelope, speeding along the process with
VERY low impact to the axis code base itself.
These streams would be specified in the configuration file or using
system properties and would be bound at run time using reflection.
I would be interested in hearing any opinions about this.
