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

Bug 313150

Summary: [Model Explorer] Stereotype applications appear in model explorer
Product: [Modeling] Papyrus Reporter: Ansgar Radermacher <ansgar.radermacher>
Component: CoreAssignee: Patrick Tessier <Patrick.Tessier>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: P3 CC: rschnekenburger
Version: 0.7.0Flags: sebastien.gerard: iplog-
Target Milestone: 0.7.0   
Hardware: PC   
OS: All   
Whiteboard:
Attachments:
Description Flags
mylyn/context/zip
sebastien.gerard: iplog+
Modification of content provider (filtering) sebastien.gerard: iplog+

Description Ansgar Radermacher CLA 2010-05-17 10:58:32 EDT 
Build Identifier: 0.7.0.v201004271830

In case of a static profile, stereotype applications appear in the model explorer before the model package starts.

Reproducible: Always

Steps to Reproduce:
1. Open a model with a static profile applied
2.
3.
Comment 1 Patrick Tessier CLA 2010-06-11 04:08:57 EDT 
I will work on that
Comment 2 Patrick Tessier CLA 2010-06-17 04:40:25 EDT 
Created attachment 172097 [details]
mylyn/context/zip

Impacted plugins
Comment 3 Patrick Tessier CLA 2010-06-17 04:43:44 EDT 
A new content provider has created in the uml modelexplorer.
The old content provider has a low priority and by default it is not displayed.

The UML content provider has a higher priority and it is used by default. It contains methods that comes from UML plugin in order to filter stereotype application.
Comment 4 Ansgar Radermacher CLA 2010-07-23 08:49:07 EDT 
The patch does not work
Comment 5 Ansgar Radermacher CLA 2010-07-23 08:52:45 EDT 
Created attachment 175062 [details]
Modification of content provider (filtering)

Modifies the getRootElements operation of the content provider. Filters returned elements: only instances of packages are returned.
Patch has been tested with stereotype application of the static profiles MARTE and FCM.
Comment 6 Ansgar Radermacher CLA 2010-09-02 05:59:20 EDT 
Now, only stereotype applications that are invalid (typically, due to a profile that is not available or has modified IDs) are shown in the model explorer. While it may still be considered as a bug, I find it rather helpful as an indication of a failed stereotype application which might otherwise remain unnoticed as "garbage" in the model.