Book a Demo

Author Topic: Round-Trip Engineering Problems  (Read 3041 times)

dsargrad

  • EA Novice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Round-Trip Engineering Problems
« on: May 19, 2010, 01:34:19 am »
We are trying to put a "round trip engineering" process into place. We have the process, but found two problems:
1] Reverse Engineering std::vector assocation lost
I have two classes coded as;

class foo { ... }
class bar : public std::vector<foo> { ... }

After reversing these into EA, there is no association link between foo
and bar, where I would have expected an aggregation or composition
relationship.

2] Forward Engineering Derivation from Template Class Corrupted

The following class was corrupted on forward generation
Original class:
class AClass : public boost::intrusive::list_base_hook<> {
}

Generated class:
class AClass : public boost::intrusive::list_base_hook {
}
« Last Edit: May 19, 2010, 02:33:01 am by dsargrad »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Round-Trip Engineering Problems
« Reply #1 on: May 19, 2010, 03:25:20 pm »
Template classes (or generics) are not (yet) supported by the forward/reverse engineering of EA.
If you need this feature please send a feature request to Sparx usign the link on the bottom of the page.
You are not the first to request this, maybe if they get enough requests they will actually develop it.

Geert