axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philipp Leitner <philipp.leit...@gmx.at>
Subject Re: Axis2 doc/wrapped service with many params
Date Mon, 23 Apr 2007 07:01:22 GMT
This is not doc/wrapped anymore if I do it like this :-/ this is more 
like rpc/encoded .

/philipp

Martin Gainty schrieb:
> Good Evening Phillip-
> try this in your wsdl..
> 
> <message name="sampleMessage"
> <part name="first" type="xsd:string">
> <part name="second" type="xsd:string">
> <part name="third" type="xsd:string">
> </message>
> <portTyle name="SomePortName">
> <operation name="someMethod">
>  parameterOrder="first second third"
> ..
> </operation>
> </portType>
> 
> HTH
> Martin--
> This email message and any files transmitted with it contain confidential
> information intended only for the person(s) to whom this email message is
> addressed.  If you have received this email message in error, please notify
> the sender immediately by telephone or email and destroy the original
> message without making a copy.  Thank you.
> 
> ----- Original Message ----- From: "Dennis Sosnoski" <dms@sosnoski.com>
> To: <axis-user@ws.apache.org>
> Sent: Sunday, April 22, 2007 5:43 PM
> Subject: Re: Axis2 doc/wrapped service with many params
> 
> 
>> Hi Philipp,
>>
>> Both the order and the names of the parameters are supposed to matter 
>> in wrapped doc/lit, since this uses an <xs:sequence> to compose the 
>> parameter elements. With JiBX data binding the names definitely 
>> matter, as is also the case with XMLBeans; if ADB doesn't care about 
>> the names this seems like a significant error in the ADB code.
>>
>>  - Dennis
>>
>> Dennis M. Sosnoski
>> SOA and Web Services in Java
>> Training and Consulting
>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>
>>
>>
>> Philipp Leitner wrote:
>>> Hi all,
>>>
>>> I just did a few experiements with an Axis2 service that I deployed. 
>>> I am using the doc/wrapped style, and have an operation that looks 
>>> something like this (in Java notation):
>>>
>>> <snip>
>>>
>>> public String concatSomeStuff(String param1, String param2, String 
>>> param3, int param4);
>>>
>>> </snip>
>>>
>>> The operation will just concatenate the parameters and return them as 
>>> String.
>>>
>>> Now I discovered that a SOAP request like this
>>>
>>> <concatSomeStuff>
>>> <param3>14</param3>
>>> <param2>Sperrgasse </param2>
>>> <param0>Philipp Leitner </param0>
>>> <param1>111</param1>
>>> </concatSomeStuff>
>>>
>>> bears a different result then a request like
>>>
>>> <concatSomeStuff>
>>> <param2>Sperrgasse </param2>
>>> <param3>14</param3>
>>> <param1>111</param1>
>>> <param0>Philipp Leitner </param0>
>>> </concatSomeStuff>
>>>
>>> (note the different order of the parameters).
>>>
>>> Meanwhile, the actual /name/ of the parameters does not seem to 
>>> matter. A request like
>>>
>>> <concatSomeStuff>
>>> <a>Sperrgasse </a>
>>> <b>14</b>
>>> <c>111</c>
>>> <d>Philipp Leitner </d>
>>> </concatSomeStuff>
>>>
>>> still works.
>>>
>>> Is this really how Axis2 (or doc-style SOAP in general) is supposed 
>>> to work? The order of the parameters is important, while the name is 
>>> not important? For some reason I always figured it should be the 
>>> other way 'round.
>>>
>>> Can somebody shed some light on this issue?
>>>
>>> /philipp
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Mime
View raw message