incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Vescovi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (YOKO-65) Generate wrapped doc style wsdl.
Date Thu, 22 Jun 2006 15:15:30 GMT
    [ http://issues.apache.org/jira/browse/YOKO-65?page=comments#action_12417320 ] 

Matteo Vescovi commented on YOKO-65:
------------------------------------

There is a problem in the <corba param: ... /> and <corba:return ...> element
in the corba binding section.
The idltype attribute is not set.

string
    greetMe(
        in string return_message
    );

results in:

<corba:operation name="greetMe">
 <corba:param mode="in" name="inparameter" />
 <corba:return name="outparameter" />
</corba:operation>

instead of the correct

corba:operation name="greetMe">
 <corba:param mode="in" name="inparameter" idltype="corba:string" />
 <corba:return name="outparameter" idltype="corba:string" />
</corba:operation>

The reason is that WSDLToCorbaBinding does not yet support comples types.
During the corba binding generation, method WSDLToCorbaBinding.processComplexType() is invoked,
but this method only returns a new CorbaTypeImpl instead of process the wrapped doc style
complex type that wraps up the parameter.

In order to have generate wrapped document style WSDL and correct corba bindings, we need
to add support for complex types to WSDLToCorbaBinding class.


> Generate wrapped doc style wsdl.
> --------------------------------
>
>          Key: YOKO-65
>          URL: http://issues.apache.org/jira/browse/YOKO-65
>      Project: Yoko - CORBA Server
>         Type: Improvement

>     Reporter: Matteo Vescovi
>     Priority: Minor
>  Attachments: WrappedDocStyle.idl, expected_WrappedDocStyle.wsdl, wrapped_doc_style.diff
>
> Change the wsdl that is being generated currently to match a wrapped doc style wsdl.
> This doesn't make a difference with the corba binding but generally it s a well accepted
design.
> For eg: Let's say the idl has the following operation:
> string
>     greetMe(
>         in string return_message
>     );
> Then the types that get generated should be:
>             <element name="greetMe">
>                 <complexType>
>                     <sequence>
>                         <element name="return_message" type="string"/>
>                     </sequence>
>                 </complexType>
>             </element>
>             <element name="greetMeResult">
>                 <complexType>
>                     <sequence>
>                         <element name="return" type="string"/>
>                     </sequence>
>                 </complexType>
>             </element>
> What we currently generate is:
> <element name="greetMe" type="string"/> & <element name="greetMeResult"
> type="string"/> which is correct but by default we should wrap it up
> with a complex type.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message