Re: Passing initliasation parameters to SOAP services

The configure method of the ConfigurableService interface is only called immediately after the constructor. It is *not* called each time a service method is called. Therefore, you could just instantiate the listener in the configure method instead of the constructor, and use an application or

Re: Passing initliasation parameters to SOAP services

Just realised that it would have been good that such parameters are accessible via the service's constructor .. or a init() method just like in servlets ... at least in the case of what I am doing, that is ... the SOAP service will need to pass on a Java object that represents the SOAP messag

RE: Keeping socket open between calls

Thanks a lot!! I'll take a look and tell you how it goes (ie. changing it to use SSL?? ) Thanks again! Luke Galea Software Development BlueCat Networks 905-762-5225 -Original Message- From: WJCarpenter [mailto:[EMAIL PROTECTED]] Sent: February 5, 2003 3:05 PM To: [EMAIL PROTECTED] Su

RE: Keeping socket open between calls

> I am finding that my attempts at writing a custom SOAP Transport are > failing as well.. so perhaps you meant the former. This is > frustrating.. Attached is HttpClientConnection.java, which is my implementation of an HTTP/1.1 Apache SOAP 2.x transport using the HTTPClient package from

Order of parsing

I have an application that is currently out in the wild that uses the Wingfoot 1.02 client library, due to a bug in this version, nested vectors are not processed correctly so I have to manualy take the information out of the incoming respose and parse it into my object... I do this by using the .g

RE: Keeping socket open between calls

The client does not support keep-alives. The server behavior with respect to HTTP things like keep-alives is governed by the Web server you are using and its configuration. On 5 Feb 2003 at 13:09, Luke Galea wrote: > Do you mean that the Apache SOAP server doesn't support keep-alives? Or > the

RE: Keeping socket open between calls

Do you mean that the Apache SOAP server doesn't support keep-alives? Or the client? I am finding that my attempts at writing a custom SOAP Transport are failing as well.. so perhaps you meant the former. This is frustrating.. I tried using pureTLS instead of JSSE.. no change.. so I think it's the

RE: Keeping socket open between calls

Thanks.. I am writing a custom soap http transport that will keep the socket open.. with any luck that will fix the problem.. Luke Galea Software Development BlueCat Networks 905-762-5225 -Original Message- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: February 5, 2003 9:57 AM T

Re: Calling SOAP with attachments from non java application

I am not sure what other implementations support attachments as RPC parameters (as opposed to just being plain attachments). Also, you should note that there are two methods for encoding attachments, MIME and DIME. Apache SOAP does MIME, as specified in the original SOAP Attachments spec. I b

Re: JDK 1.3.0

I do not know of any problems with specific JDKs. On 5 Feb 2003 at 17:39, Jesus M. Salvo Jr. wrote: > > Is anyone aware of any problem using Apache SOAP with JDK 1.3.0 instead > of JDK 1.3.1? > > SunOne WebServer 6 does not seem to support 1.3.1 ... only specific > build of 1.2.2, 1.3.0 and 1

Re: AW: zipping Soap URGENT

Is this existing code that works with another version of Apache SOAP but not the nightly build? If so, can you post the code? On 4 Feb 2003 at 18:29, Malte Kempff wrote: > Hi Scott > Thank you for the hint. > But since I am trying the new soap-version form nightly build of SOAP > (2.2.2002) > I

Re: Keeping socket open between calls

Apache SOAP explicitly closes sockets after each request as it does not support HTTP keep-alives. The frequent handshaking is, I believe, caused by JSSE or JDK 1.4 marking cached sessions as stale very quickly. I have run tests in which a cached SSL session is re-used anywhere from 0 to 6 times o

RE: None of the matching operations for soapAction...

I notice in the WSDL Have you tried setTargetObjectURI("http://tempuri.org/message/";)? On 4 Feb 2003 at 8:53, Sean Leblanc wrote: > Is that not the right action? The WSDL has a section like this: > > > soapAction="http://tempuri.org/action/SOAPOrder.GetNewOrders"/> > - > > http://