Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360104

Summary:	[Palettes] Problems with 'applied sterotypes' post-action
Product:	[Modeling] Papyrus	Reporter:	Alexandre Cortier <alexandre.cortier>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	arthur.daussy, papyrus-bugs, rschnekenburger
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Alexandre Cortier

2011-10-06 10:27:28 EDT

Build Identifier: Eclipse ID : 20110916-0149, Papyrus version : 0.8.1.v201109301802

There is a problem with apply stereotype EditPolicy. Some EditPart don't inherit from NamedElementEditPart and so they do not have the EditPolicy.
Below, a list of objects on which the 'applied sterotype' post-action don't work (ActivityDiagram): 
- AcceptEventAction 
- AddVariableValueAction
- LoopNode
- ConditionalNode
- AddVariableValueAction
- AddStructuralFeatureValueAction
- OpaqueAction

Reproducible: Always

Steps to Reproduce:
1.Define a custom palette
2.Use one of the listed object and apply sterotypes
3.Try your new customized palette

Comment 1 Arthur Daussy

2012-01-23 11:50:16 EST

+ final Node

Comment 2 Benoit Maggi

2017-09-01 09:19:00 EDT

The current recommended way to customize palette is to use element type (no more post palette action)