axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <>
Subject Problem with parameter order on server side
Date Mon, 07 Jan 2002 18:34:05 GMT
It looks like we've got a parameter order problem on the server.  AXIS
assumes an order.  SOAP messages do not guarantee any order.  Assume we
have the following interface:

public interface iface {
    public void op(String p1, int p2);

When a SOAP message for this call is received by the server-side
RPCProvider.processMessage, it ignores the p1 and p2 names and assumes that
its args and argValues lists have an order.  This is bad.  If the client
were an AXIS client, then we have no problems, but if the client put the
parameters onto the SOAP message in the reverse order (which is perfectly
legal since there's no implied order in the SOAP message), then AXIS will
look for a method with the parameters reversed and barf.  In general, with
any method that has more than one parameter, AXIS assumes an order, and if
the SOAP message order is not the same, the chances are good that there
will be some runtime exception.

How can we fix this?  Two possibilities:
1.  deploy the service with method parameter names;
2.  let the skeleton figure it out; AXIS could give the skeleton a Map of
the parameters and the skeleton would pull them out by name and make the
call to the implementation in the proper order.

Comments?  Any other solutions?

Russell Butek

View raw message