axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Fell <>
Subject Re: Problem with parameter order on server side
Date Tue, 08 Jan 2002 02:55:24 GMT
Both Order & Names are important, especially when you take into
account the missing element is default/null rule as well. If you work
purely from one or the other, you'll run into trouble eventually


On Mon, 7 Jan 2002 15:05:34 -0600, in soap you wrote:

>Hmmmm...  Before now I've had it pounded into my head that there is no
>guarantee of order in the SOAP message, so I'm going to have to twist my
>frame of mind before I'm fully comfortable with this.  I THINK I've finally
>digested this part of the spec (you're not the first to try getting this
>through my thick skull).  From this section I get the impression that AXIS
>is doing it right, that it doesn't care at all what the names are when
>we're pulling the args from the message (though I still think it's best to
>put the names in the message if we have them, which we DO do).
>Russell Butek
>"Simon Fell" <> on 01/07/2002 12:51:35 PM
>Please respond to
>To:   <>
>Subject:  Re: Problem with parameter order on server side
>----- Original Message -----
>From: "Russell Butek" <>
>To: <>
>Sent: Monday, January 07, 2002 10:34 AM
>Subject: Problem with parameter order on server side
>> 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:
>That depends on whether you're doing section 7 RPC or not, 7.1 bullet 3 is
>"Each [in] or [in/out] parameter is viewed as an accessor, with a name
>corresponding to the name of the parameter and type corresponding to the
>type of the parameter. These appear in the same order as in the method
>So for section 7 RPC, both name and order are important.

View raw message