AW: Compressing SOAP requests and using SSL

"Malte Kempff" <[email protected]>
Newsgroups gmane.text.xml.soap.user
Message-ID <[email protected]>
Hi Nigel,
I am using soap2.3.1 for RPCs
calling the methods takes as far I remember not very much changes
and it is looking somehting like this:

...
SOAPHTTPConnection st = new SOAPHTTPConnection();
...
SOAPContext ctx = new SOAPContext();
ctx.setGzip(true);
Call call = new Call(m_soapServiceName,
                     callName,
                     params,
                     null,
                     Constants.NS_URI_SOAP_ENC,
                     ctx
                    );
call.setSOAPTransport(st);
...

Butyou also need to enhance the soap depoloy discriptor looking something
like this:

   <isd:provider type="java"
                  scope="Application"
                  methods= "...">
    ...
	<isd:option key="gzip" value="true"/>
    ...
  </isd:provider>


good luck hope it helps

Malte


-----Ursprungliche Nachricht-----
Von: Nige White [mailto:[email protected]]
Gesendet: Mittwoch, 10. November 2004 16:22
An: [email protected]
Betreff: Re: Compressing SOAP requests and using SSL


OK, looking at the soucre code, it looks like I should extend
SOAPHTTPConnection, and override send() using an extended version of
HTTPUtils in which I implement postCompressed().

I already extend SOAPHTTPConnection so that I can share a
SOAPHTTPConnection between several generated client classes (I keep
count of how many disconnect from it, and when there are none left, I
send a shutdown call to the server), so it's not a big deal.

A few things though. I'm trying to use explicit imports (Isn't it bad
style to import "...*"?) The latest source of SOAPHTTPConnection.send()
references a Cookie class. There is no Cookie class in my SOAP which is
2.3.1. There is a Cookie class in the source archives, but it's new.
Which version of SOAPHTTPConnection should I go back to? Or should I
pull out the latest source of Cookie, and use that?

Is this a good approach? I want to keep my client classes simply using
Call.invoke(), so the change must be invisible to that level.

Nigel

PS: Any help on the "No serializer" question I posted? I tagged it onto
the tail end of Vladimir's thread. Thanks!

_____________________________________________________________________
This message has been checked for all known viruses. Virus scanning
powered by Messagelabs http://www.messagelabs.com For more information
e-mail : [email protected]



____________
Virus checked by G DATA AntiVirusKit
Version: AVK 15.0.815 from 03.11.2004
Virus news: www.antiviruslab.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.