Hi Thomas I have tried and I found it easier to create a different Call instance everytime. My understanding is:-
That Call object is stateful. You can add parameters,headers,attachements to it. Once you invoke a SOAP request with this Call object and then if you want to use it again you need to make sure all the previous properties that you set on Call object have to be reset to make it a blank request. If you don't mind doing that after invocation of each SOAP request you can use it. Akhil ----- Original Message ----- From: "Haug Thomas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 01, 2003 7:49 AM Subject: AW: Concurrent usage of the Call object ? Hi Jennifer and Sumit, thanks for your advise: this is exactly what I have already suspected. So my question shifts a little bit : if a client wants to issue several requests concurrently, is it sufficient to create a separate Call object for each thread ? HAs anybody tried that before ? Thanks, Thomas > -----Urspr�ngliche Nachricht----- > Von: Jackson, Jen (CCI-Atlanta) [mailto:[EMAIL PROTECTED] > Gesendet am: Montag, 30. Juni 2003 14:32 > An: [EMAIL PROTECTED] > Betreff: RE: Concurrent usage of the Call object ? > > Hi Thomas. My understanding is that the Call object is a > stateful object, containing the soap request and response. > The Serializer and Deserializers contains the request and > response data within the call object. So I would say you > need to create a call per soap request. > > Anyone else? > > Jennifer Jackson > Programmer/Analyst > > -----Original Message----- > From: Haug Thomas [mailto:[EMAIL PROTECTED] > Sent: Monday, June 30, 2003 8:27 AM > To: '[EMAIL PROTECTED]' > Subject: Concurrent usage of the Call object ? > > > Hi everbody, > > I have a question regarding the org.apache.axis.client.Call > class. Is it > possible that a client creates only one Call instance and than issues > serveral requests through this object concurrently or is this > kind of usage > illegal ? > > Thanks, > Thomas >
