axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anne Thomas Manes" <atma...@gmail.com>
Subject Re: question on doc/lit wrapped wsdl with one-way operations
Date Fri, 12 Oct 2007 08:44:03 GMT
If you want doc/lit wrapped, then you must have an output message with
an empty wrapper element.

Other options for a void return:

If you have an empty output message (message defined but containing no
parts), then it will be treated doc/lit unwrapped with a
request/response MEP -- it will return faults if you define them.

If you have no output message (no message defined), then it will be
treated like doc/lit unwrapped with a one-way MEP -- it provides no
means to return a fault.

Anne


On 10/8/07, Shantanu Sen <ssen@pacbell.net> wrote:
> What is the right way of developing a WSDL (with doc/lit wrapped binding) that describes
operations that have void returns?
>
> One approach is to have no output message as shown below
>
> ===
>  <complexType name="allvoid">
>   <sequence />
>   </complexType>
>  <complexType name="returnvoid">
>  <sequence>
>   <element name="int_1" type="int" />
>   </sequence>
>   </complexType>
>   <element name="allvoid" type="tns:allvoid" />
>   <element name="returnvoid" type="tns:returnvoid" />
>   </schema>
>   </types>
>
>   <part element="tns:allvoid" name="allvoid" />
>   </message>
>  <message name="Testvoid_returnvoid">
>   <part element="tns:returnvoid" name="returnvoid" />
>   </message>
>  <portType name="Testvoid">
>  <operation name="allvoid">
>   <input message="tns:Testvoid_allvoid" />
>   </operation>
>  <operation name="returnvoid">
>   <input message="tns:Testvoid_returnvoid" />
>   </operation>
>   </portType>
>
> ===
>
> The other one is to have an output message with an empty wrapper element.
>
> ====
> <complexType name="allvoid">
>     <sequence/>
>    </complexType>
>    <complexType name="allvoidResponse">
>     <sequence/>
>    </complexType>
>    <complexType name="returnvoid">
>     <sequence>
>      <element name="int_1" type="int"/>
>     </sequence>
>    </complexType>
>    <complexType name="returnvoidResponse">
>     <sequence/>
>    </complexType>
>    <element name="allvoid" type="tns:allvoid"/>
>    <element name="allvoidResponse" type="tns:allvoidResponse"/>
>    <element name="returnvoid" type="tns:returnvoid"/>
>    <element name="returnvoidResponse" type="tns:returnvoidResponse"/>
>   </schema>
>  </types>
>  <message name="Testvoid_allvoidResponse">
>   <part element="tns:allvoidResponse" name="allvoidResponse"/>
>  </message>
>  <message name="Testvoid_returnvoidResponse">
>   <part element="tns:returnvoidResponse" name="returnvoidResponse"/>
>  </message>
>  <message name="Testvoid_allvoid">
>   <part element="tns:allvoid" name="allvoid"/>
>  </message>
>  <message name="Testvoid_returnvoid">
>   <part element="tns:returnvoid" name="returnvoid"/>
>  </message>
>  <portType name="Testvoid">
>   <operation name="allvoid" >
>    <input message="tns:Testvoid_allvoid"/>
>    <output message="tns:Testvoid_allvoidResponse"/>
>   </operation>
>   <operation name="returnvoid">
>    <input message="tns:Testvoid_returnvoid"/>
>    <output message="tns:Testvoid_returnvoidResponse"/>
>   </operation>
>  </portType>
> ===
>
> Is there any 'standard' for describing this type of operation using doc/lit (wrapped)
mode?
>
> Note the example is just for test purposes - it should have multiple parameters for warranting
a doc/lit wrapped style.
>
> Thanks,
> Shantanu  Sen
>
>
>
> ---------------------------------------------------------------------
> 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