UML14 and UML2 metafacades require inconsistent type hierarchy implementation
hierarchies
-----------------------------------------------------------------------------------------
Key: UMLMETA-102
URL: http://jira.andromda.org/browse/UMLMETA-102
Project: UML Metafacades
Issue Type: Bug
Affects Versions: 3.4-SNAPSHOT
Environment: AndroMDA 3.4-SNAPSHOT
Reporter: Bob Fields
Assignee: Bob Fields
Fix For: 3.4-SNAPSHOT
Several metafacade datatypes have different inheritance hierachies between
UML14 and UML2 underlying metamodel. For example, the following inherit from
Classifier instead of ModelElement: Event/CallEvent, Interaction, StateMachine.
TemplateParameter implementation does not work at all in UML2. We need a way to
specify one inheritance hierarchy (generalization class) for UML14 repository
implementation, and another hierarchy for UML2, for error free migration
between the different UML types. Is it even possible to have different
hierarchies with a single common metafacade library?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
