do u have a patch in mind as well? -- dism
On Sat, 10 Jul 2004 01:23:30 +0530, sanjay <[EMAIL PROTECTED]> wrote: > Thanks, > I filed a bug for this [AXIS-1445] > > Regards > Sanjay > > > > -----Original Message----- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 10, 2004 12:51 AM > To: [EMAIL PROTECTED] > Subject: Re: Service.createCall() - Is this a bug ? > > looks like a bug....please submit a bug report with a small test case > if possible., > > -- dims > > ----- Original Message ----- > From: sanjay <[EMAIL PROTECTED]> > Date: Fri, 9 Jul 2004 23:07:12 +0530 > Subject: Service.createCall() - Is this a bug ? > To: [EMAIL PROTECTED] > > Hi > > Service.createCall is > overloaded with following methods - > > 1. Service.createCall(QName portName) > > 2. Service.createCall(QName portName, > QName operationName) > > 3. Service.createCall() > > If I call (1) and then - call.setOperationName() it > works fine. > > If I call (2) and it doesn't work, even if I > explicitly set operationName again > > Calling (3) and setting everything explicitly works fine. > > I looked in code - Service.java > > public javax.xml.rpc.Call createCall(QName portName, > > 1. QName operationName) > > throws ServiceException { > > Call call = (org.apache.axis.client.Call) > createCall(); > > call.setOperation(portName, operationName.getLocalPart()); > > return > (call); > > } > > Should line 3 be - createCall(portName) instead of createCall() > ? > > Because createCall(QName) is doing all the > initialization. > > API Documentation says methods > 1,2 prefill as much data from WSDL as possible. > > Or am I missing something ? > > Regards > > Sanjay > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ > > -- Davanum Srinivas - http://webservices.apache.org/~dims/
