Well, I suppose you understand your objectives (e.g. target market) better than I. I am just sharing my experience, specifically that a number of users have put SOAP 2.2 into production and are wary of upgrading. In some cases, an upgrade would require an upgrade of other components (e.g. a newer rev of WebSphere), in others it's an "if it ain't broke, don't fix it" culture. Given that I still see a lot of Oracle 7, SQL Server 6.5, NT 4, SunOS 2.4, etc., in production even now (I consult in Philadelphia USA, a large city but not exactly cutting edge), I don't know that the SOAP 2.2 installed base will go away soon. Of course, whether these organizations are likely WSIF adopters is another matter entirely!
Scott Nichol ----- Original Message ----- From: "Anthony Elder" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 6:33 AM Subject: Re: [wsif] using the apache soap provider and a proxy server > > Thanks for that info Scott. > > Incidentally, currently WSIF only works with SOAP 2.3.1. We don't have any > plans to change this at the moment, are you saying you think we should? > > ...ant > > Anthony Elder > [EMAIL PROTECTED] > Web Services Development > IBM UK Laboratories, Hursley Park > (+44) 01962 818320, x248320, MP208. > > > Scott Nichol <[EMAIL PROTECTED]> on 19/09/2002 16:01:20 > > Please respond to [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: > Subject: Re: [wsif] using the apache soap provider and a proxy server > > > > Anthony, > > You have not missed anything. Adding support for http.* and https.* > properties is on my personal to-do list for SOAP, but I have not made it > down to that item. > > Even if/when it is added, a large portion of the Apache SOAP user base > seems > to be locked into a particular version, notably 2.2. Therefore, I think > you > may want to consider adding the code to WSIF to accomodate this community. > > Scott Nichol > > ----- Original Message ----- > From: "Anthony Elder" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 19, 2002 10:30 AM > Subject: [wsif] using the apache soap provider and a proxy server > > > > Currently the wsif apache soap provider doesn't work via a proxy server > as > > the Java http.proxyHost and http.proxyPort seemed to be ignored by SOAP, > on > > the other hand the axis provider works fine through a proxy > automatically. > > > > I thought I could easily change this by adding code to the apache soap > wsif > > operation to extract the Java system properties and setting them in the > > SOAPHTTPConnection with the setProxyHost/setProxyPort methods, but then > it > > doesn't work for the localhost. Presumably I also need to take account of > > the http.nonProxyHosts system property, and have something like the axis > > CommonsHTTPSender.isHostInNonProxyList method. And a match method to take > > care of wildcards... > > > > Probably a question for the soap list, but before I do all this does > anyone > > know if this really is the case or is there something already implemented > > in apache soap to do this which I've missed? > > > > ...ant > > > > Anthony Elder > > [EMAIL PROTECTED] > > Web Services Development > > IBM UK Laboratories, Hursley Park > > (+44) 01962 818320, x248320, MP208. > > > > > > > > >
