Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 265703 - Regenerate UMLSwitch to fix base class ordering
Summary: Regenerate UMLSwitch to fix base class ordering
Status: CLOSED FIXED
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: M6   Edit
Assignee: James Bruck CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 265365
Blocks: 247980
  Show dependency tree
 
Reported: 2009-02-20 15:25 EST by Dave Steinberg CLA
Modified: 2009-03-24 18:13 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Steinberg CLA 2009-02-20 15:25:48 EST
In UMLSwitch, the RedefinableElement is coming after the NamedElement and Element cases for some elements. This is wrong: as the most general base types in UML, NamedElement and Element should be the last cases. The issue was found in Port, Reception, BehavioralFeature, Operation, Property and possibly more.

Bug 265365 fixed the ordering problem was fixed in EMF. The UML metamodel must be regenerated to pick up this fix.
Comment 1 James Bruck CLA 2009-02-21 08:53:45 EST
Thanks Dave, I'll regenerate UML2.  
I believe this may impact anyone who depends on generated switch statements.   Should others be notified of this change?

Comment 2 Dave Steinberg CLA 2009-02-23 09:51:52 EST
I'm not sure that this is more or less deserving of attention than any other bug in generated code that we've fixed before. If people are affected by this problem, it will be fixed for them when they regenerate. If they aren't, they won't notice.

Given that it took so long for the bug to be reported, I would guess most people fall in the latter category.
Comment 3 James Bruck CLA 2009-02-27 15:17:22 EST
Committed Feb 27 2009
Comment 4 James Bruck CLA 2009-03-24 18:13:02 EDT
.