I have a simple jws webservice with a function that subtracts value B from value A. The ordering in the wsdl for this service is valueA valueB:

<wsdl:operation name="testOrder" parameterOrder="valueA valueB">

To call this service I set the IN parameters, first valueB, then valueA using:
call.addParameter("valueB".....) ;
call.addParameter("valueA",....) ;


I add an object array to this on invoke with the values:
obj[0] = 10 ;
obj[1] = 20 ;

Naturally you would expect an order agnostic API to ignore my ordering of the parameters and correctly order it for the wsdl, so in fact the parameters are passed valueA valueB as requested in the WSDL. (afterall they are named parameters so this shouldn't be too difficult).

I've found that this is not the case, order is important and my answer from this operation is -10, not 10 - is this a known bug in the Axis 1.1 API?

Thanks,

Benjamin

Reply via email to