incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Vescovi (JIRA)" <>
Subject [jira] Updated: (YOKO-97) Support for exceptions
Date Fri, 28 Jul 2006 16:20:14 GMT
     [ ]

Matteo Vescovi updated YOKO-97:

    Attachment: exception_and_basic_struct_support.diff

attached is a patch to add support for IDL exception and struct types to IDLToWSDL tool.

The attached zip archive contains two new source files and
which should be placed in (all paths rooted at trunk):

Four new resource files needed for new tests I added are also in the zip archive; these should
be placed in:

Please examine the contents of the resource files before considering applying this patch.
I am not 100% sure that the generated wsdl is correct and would like someone more familiar
with wsdl than I am :-) to ensure everything is fine.

In particular, in expected_Exception.wsdl generated from Exception.idl, the complexTypeS representing
each idl exception are wrapped by an element.
I couldn't get XmlSchema to create the following wsdl fragment:
<complexType name="ExternalException">
        <element name="description" type="string"/>
<element name="ExternalException" type="ExternalException"/>

Instead, I have the following:
<xs:element name="ExternalException">
  <xs:complexType name="ExternalException">
      <xs:element name="description" type="xs:string">
Is this correct?

If there are any problems, I'll gladly fix them and create a new patch.

- Matteo

> Support for exceptions
> ----------------------
>                 Key: YOKO-97
>                 URL:
>             Project: Yoko - CORBA Server
>          Issue Type: Sub-task
>          Components: Idl2Wsdl
>    Affects Versions: 1.0-incubating-M1
>            Reporter: Balaji Ravi
>         Attachments: exception_and_basic_struct_support.diff,
> Map the idl exceptions to a wsdl fault, a struct schema type & a corba:exception
type map.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message