Ken Lodge wrote:
>
> Consider the following wsdl fragment (note parameterOrder not specified):
>
> <message name="myRequest">
> <part name="arg1" type="xsd:string"/>
> <part name="arg2" type="xsd:int"/>
> </message>
> <message name="myResponse">
> <part name="arg2" type="xsd:int"/>
> </message>
> <portType name="myPortType">
> <operation name="myOperation">
> <input message="tns:myRequest"/>
> <output message="tns:myResponse"/>
> </operation>
> </portType>
As per section 4.3.4, If parameterOrder is not specified, all parts
are considered unlisted. Unlisted parts appear (after the listed
parts, none in this case) in the order in which these parts appear
in the message--first, input message parts and next, output message
parts. If an unlisted part is an INOUT parameter, then it appears in
the order in which is the corresponding part appears in the input
message. So following this rule, the method signature is:
void myOperation(String arg1, IntHolder arg2)
Regards,
Rahul
> In section 4.3.4 WSDL Operation, under the WSDL parameterOrder subheading,
> there are 2 rules applicable here:
>
> [1] "If a part name appears in both the input and output message
> with the same type, it is an inout parameter"
>
> [2] "If there is a single unlisted [in parameterOrder attribute ] output
> part,
> then it is the return type. Otherwise, the return type is void."
>
> Rule [1] indicates arg2 should be treated as an inout, with void return
> type.
> But rule [2] indicates that there should be a return type of int (and 2
> input
> parameters - arg1 and arg2).
>
> My guess is to treat arg2 as an inout, but I cannot find any part of the
> spec
> to confirm this, and no direct discussion of it in the interest group
> archive.
> Am I missing something ?
>
> Thanks,
> Ken.
>
> Ken Lodge
> Cape Clear Software
> 61 Fitzwilliam Lane, Dublin 2
> ph: +353-1-2419955
>
> CAPE CLEAR named in Red Herring 100:
> www.redherring.com
>
> CAPE CLEAR named as top 10 private software firm:
> www.venturewire.com
>
> CAPE CLEAR awarded "Next Big Thing" at Enterprise 2002:
> www.capeclear.com/news/press_releases/reports/next_big_thing.shtml