Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 471135 - [Elementtype] Elementtype naming problem upon creation.
Summary: [Elementtype] Elementtype naming problem upon creation.
Status: RESOLVED WONTFIX
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 471134
  Show dependency tree
 
Reported: 2015-06-26 09:49 EDT by Onder Gurcan CLA
Modified: 2017-06-19 06:53 EDT (History)
4 users (show)

See Also:

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 Onder Gurcan CLA 2015-06-26 09:49:56 EDT 
When an new element is created, it is not possible set its name inside its correspnding EditHelperAdvice. Another advice, executed always after this advice, is overriding the given name.
Comment 1 Camille Letavernier CLA 2015-06-26 11:10:07 EDT 
This should be handled by the NamingService when available (So that it can remain customizable)
Comment 2 smaoui asma CLA 2016-04-08 08:08:31 EDT 
Hello, yes I noticed this when fixing Bug 484638 in Papyrus RT. In fact, the ApplySterotype command override the name , it is executed after the configure command. to disable this, there is a boolean property "Update name" in the Apply Steroptype Configure Advise that should be set to false.
Comment 3 Remi Schnekenburger CLA 2016-07-20 09:49:22 EDT 
Set as won't fix, as there is not a real bug underneath this precise task.

If some concrete bug has to be worked on, a new bug will be opened.