Bug 518787 - Improve the org.eclipse.sirius.ui.uiSessionFactory extension point
Summary: Improve the org.eclipse.sirius.ui.uiSessionFactory extension point
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 5.0.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-06-26 10:50 EDT by Florent Latombe CLA
Modified: 2017-06-27 04:33 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 Florent Latombe CLA 2017-06-26 10:50:16 EDT
The "uiSessionFactory" extension point defined in plug-in org.eclipse.sirius.ui allows developpers to contribute their own UISessionFactory implementation.

In the schema of this extension point, extensions may defined a "String" value labelled "override" to specify the ID of another uiSessionFactory extension that must be overridden.

There are two issues with this definition of the extension point. 

1) The overridden IDs are specified as Strings and not identifiers. I am unsure whether this was intended or not.

3) In some cases, an extension may need to override several other extensions. The current workaround is to define several extensions providing the same UISessionFactory but overridding the different extensions. Ideally, one should be able to specify several IDs to override.
Comment 1 Laurent Fasani CLA 2017-06-27 04:33:43 EDT
1)Effectively, the override attribute should be an identifier as it overrides the id attribute of the extension. Note that, currently, the id attribute is declared as string and should also be a identifier.

3)Yes "Ideally, one should be able to specify several IDs to override." but it is very easy to define as many extension elements as extension you want to override especially because there are few extensions to override.

In conclusion, your request is valid but will have a very low priority for the next releases.
I do not rule out neither the fact that this ticket could be closed as "won't fix". I will let the product manager state.