Bug 496290 - Custom bundled image shapes can not be defined and tested in the same runtime
Summary: Custom bundled image shapes can not be defined and tested in the same runtime
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 4.0.0   Edit
Hardware: PC Windows NT
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-06-17 05:34 EDT by Frédéric Madiot CLA
Modified: 2016-07-01 04:04 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric Madiot CLA 2016-06-17 05:34:16 EDT
When the VSM is defined and tested in a runtime, Custom bundled image shapes are not visible.
Would it be possible to apply the same mechanism as Java services, which can now be defined and tested in the same runtime ?

Other point: in the documentation, the sentence "The image label displayed in VSMs (suffixed with the plug-in name where the bundled image shape extension is declared)." is ambigous.
I suggest to rewrite it as follows: "The image label displayed in VSMs (it will be suffixed with the plug-in name where the bundled image shape extension is declared).
Comment 1 Cedric Brun CLA 2016-06-21 04:21:05 EDT
(In reply to Frederic Madiot from comment #0)
> When the VSM is defined and tested in a runtime, Custom bundled image shapes
> are not visible.
> Would it be possible to apply the same mechanism as Java services, which can
> now be defined and tested in the same runtime ?
> 

Possible but not trivial. If we want fidelity with the behavior once deployed that would require parsing the extension point and to plug it in a way that we are 100% sure it won't interfere with the normal operation once deployed. For the Java services this is achieved with a specific extension point which is only implemented by a plugin in the specifier support or we would risk interfering and would add a dependency to PDE pretty deep down in the stack.