Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346244 - Same name for transition point and transition will prevent from saving the model
Summary: Same name for transition point and transition will prevent from saving the model
Status: CLOSED FIXED
Alias: None
Product: eTrice
Classification: Modeling
Component: UserInterface (show other bugs)
Version: 0.1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: 0.1.0
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-18 09:40 EDT by Thomas Jung CLA
Modified: 2011-12-16 02:45 EST (History)
1 user (show)

See Also:
hrr: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Jung CLA 2011-05-18 09:40:54 EDT 
If you choose to take the same name for the transition point and the transition, the madel becomes invalid. This might be ok as long as the user will be informed about that imidiatly. But currently the user recognise the fault later on, when he tries to save the model. And this could be much later and he loses all the work.
Comment 1 Henrik Rentz-Reichert CLA 2011-05-18 09:54:36 EDT 
That's a good point and definitely a cause of "empty models" as we observed them previously!

Xtext uses nested namespaces and requires all elements inside a namespace to have a unique name - regardless of their types. So all transitions, transition points, choice points and states have to be checked.
Similar for the actor structure.

We will have extend the explicit checking correspondingly.
Comment 2 Henrik Rentz-Reichert CLA 2011-05-19 11:41:11 EDT 
fixed with
27e6871f2019a1af00320e8872d085d44bd3f67d
Comment 3 Henrik Rentz-Reichert CLA 2011-12-16 02:45:35 EST 
closed resolved bug