Author Topic: MDG CORBA Add-In Reverse Engineering IDL files  (Read 4647 times)

davisford

  • EA User
  • **
  • Posts: 63
  • Karma: +0/-0
    • View Profile
MDG CORBA Add-In Reverse Engineering IDL files
« on: December 21, 2004, 12:00:23 pm »
Hello, I am trying to use the CORBA Add-In to reverse Engineer an IDL file.  However, when I do so, the parser complains that it finds an unexpected symbol.  The symbols it complains about are the bracket "[" and the const declaration.  I am admittedly not a CORBA expert, but the syntax and semantics seem to be ok with those symbols/declarations...at least as far as I understand.

The IDL file I am trying to reverse engineer is available from the OMG here: http://www.omg.org/cgi-bin/doc?ptc/04-04-13

Am I doing something incorrect here?

Thanks in advance,
Davis

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8083
  • Karma: +118/-20
    • View Profile
Re: MDG CORBA Add-In Reverse Engineering IDL files
« Reply #1 on: December 21, 2004, 01:18:24 pm »
No, you aren't doing anything wrong.  There were a few problems with the IDL parsing that the addin provided. All the ones that have been reported have been fixed, except that a new version of the addin has not yet been released.  I plan to do a little pushing for it to be released soon.

I just checked and the file you linked to can be imported with the updates.

Simon

davisford

  • EA User
  • **
  • Posts: 63
  • Karma: +0/-0
    • View Profile
Re: MDG CORBA Add-In Reverse Engineering IDL files
« Reply #2 on: January 01, 2005, 03:44:57 pm »
Hi Simon -- I have tested your updates a bit and I do have success in importing that particular IDL file.  However, it seems that the plugin ignores constants.  If you take a look at that IDL file, you'll note there are a number of const declarations.  I would think it the plugin should reverse engineer these declarations into <<CORBAConstant>> stereotyped attributes.

As it stands, I manually created a new class called ModuleConstants.  I stereotyped the class as <<CORBAConstants>>.  I then added all the const declarations as attributes to this class with stereotype <<CORBAConstant>>, with the correct type and the initial value filled in.  I also tick the const box in the tool.

I am following what I understand the mapping to be from the OMGs UML Profile for CORBA v1.0 spec.

Is it possible in an updated release to automate this process, or am I not interpreting the mapping correctly?

Thanks,
Davis