incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mosur Ravi, Balaji" <>
Subject RE: [jira] Updated: (YOKO-52) Support for primitives in the IDLToWSDL tool
Date Thu, 15 Jun 2006 17:46:03 GMT
Thanks matteo... This gets us much closer to supporting all the
primitive types in our idltowsdl tool...

I will apply the patch...

- Balaji

-----Original Message-----
From: Matteo Vescovi (JIRA) [] 
Sent: Thursday, June 15, 2006 1:03 PM
Subject: [jira] Updated: (YOKO-52) Support for primitives in the

     [ ]

Matteo Vescovi updated YOKO-52:


CORRECTED: previous patch contains a typo. I apologize.
Please ignore patch `support_for_primitive_types_except_any_type.diff'.

Attached is the patch to add support for primitives types.

The patch was created by running `svn diff >
corrected_support_for_primitive_types_except_any_type.diff' command in
an updated working copy of the repository.

As part of this patch I created a new class defined in file This is not reflected in the patch file. I
am attaching file separately. It should be
placed in

The new test I added for the new types requires two new files in the
resource directory. This is not reflected in the patch file, so I am
attaching them separetely. Files primitives.idl and
expected_Primitives.wsdl should be added to
yoko/trunk/tools/src/test/resources/idl/ directory.

The any type is not yet supported. I will raise a JIRA issue and fix it
after this patch has been merged.

This patch also includes changes to allow the PortTypeVisitor to visit
more than one idl operation in an idl interface.

> Support for primitives in the IDLToWSDL tool
> --------------------------------------------
>          Key: YOKO-52
>          URL:
>      Project: Yoko - CORBA Server
>         Type: Sub-task

>     Reporter: Balaji Ravi
>  Attachments:,
expected_Primitives.wsdl, primitives.idl,
> Implement the IDLToWSDL command line tool & add support for the

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