Corrections for CORBA IDL Code GenerationTemplates

[Ma-Lik]

Necessary corrections for the CORBA IDL are provided at http://www.itarchitect.co.uk/enterprise/display.asp?id=394. Why aren't they integrated in the CORBA IDL Addin?  

[Eve]

What I see there, are some issues which are matters of personal style.  Others are not errors of the existing templates but that the templates are expecting you to do something that you arne't.

• There is no recognition of the UML associations; hence attributes for these associations are not generated in the IDL. - There certainly should be, but some options will effect where these are used and not all types generated make use of attributes.  (I noticed that you modified the LinkedAttribute template.  This is for attributes created from associations)
  
• Syntax error in the IDL code generated for an operation that raises an exception. (The Exception name is not enclosed in brackets) - EA is expecting the list of possible exceptions surrounded by brackets as this is how it is reverse engineered.
  
• Incorrect code generated for a CORBA union; the keyword case is omitted in the generated code. - Again, the tagged value is expected to include the case keyword, as is done by reverse engineering.
  
• Each value in a CORBA enumeration is listed on a separate line – not an error, but an unconventional arrangement of code; - As I said, style issue only.  Exactly why templates are customisable.

For anything else, I'd recommend contacting sparx support directly.

As for the 'Generate CORBA Elements', you can easily write a transformation equivalent to this command and much better.  The addin was developed before transformations were available in EA.

[Ma-Lik]

OK thanks for the advices.