We discussed this a few weeks ago. If you don't specify anything (no parameters or returnType) then AXIS makes some guesses as to what it sends/returns. When you specify ANYTHING, you have to specify EVERYTHING. So if you specify a parameter and you don't specify a returnType, then AXIS assumes there is no returnType. Right now it doesn't fail if there IS a returnType, it just returns null. I wonder if an exception should be thrown?
Russell Butek [EMAIL PROTECTED] Glen Daniels <[EMAIL PROTECTED]> on 03/13/2002 12:40:30 PM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: cvs commit: xml-axis/java/samples/userguide/example2 CalcClie nt.java Russell: Any clue why we need this? Are we not sending xsi:types by default? I'm not saying it's bad, just that it used to work without it, I think. --G > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 13, 2002 12:07 PM > To: [EMAIL PROTECTED] > Subject: cvs commit: xml-axis/java/samples/userguide/example2 > CalcClient.java > > > butek 02/03/13 09:06:33 > > Modified: java/samples/userguide/example2 CalcClient.java > Log: > Fixed the sample. > > Revision Changes Path > 1.9 +1 -0 > xml-axis/java/samples/userguide/example2/CalcClient.java > > Index: CalcClient.java > =================================================================== > RCS file: > /home/cvs/xml-axis/java/samples/userguide/example2/CalcClient.java,v > retrieving revision 1.8 > retrieving revision 1.9 > diff -u -r1.8 -r1.9 > --- CalcClient.java 4 Jan 2002 22:30:03 -0000 1.8 > +++ CalcClient.java 13 Mar 2002 17:06:33 -0000 1.9 > @@ -93,6 +93,7 @@ > call.setOperationName( method ); > call.addParameter( "op1", XMLType.XSD_INT, > ParameterMode.PARAM_MODE_IN ); > call.addParameter( "op2", XMLType.XSD_INT, > ParameterMode.PARAM_MODE_IN ); > + call.setReturnType( XMLType.XSD_INT ); > > Integer ret = (Integer) call.invoke( new Object [] > { i1, i2 }); > > > > >