Bug 487490

Summary:	[Model Explorer] [Facet] Associations in Model Explorer are not collected together in a folder (Simple UML Facet)
Product:	[Modeling] Papyrus	Reporter:	Ronan Bar <ronan.barrett>
Component:	Core	Assignee:	Camille Letavernier <cletavernier>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	papyrus-bugs, rschnekenburger
Version:	1.1.2	Keywords:	usability
Target Milestone:	---
Hardware:	PC
OS:	All
See Also:	https://git.eclipse.org/r/97472 https://git.eclipse.org/r/111065
Whiteboard:	dx

Description Ronan Bar

2016-02-09 04:30:26 EST

Other tools collect all the associations together in a folder in the "Model Explorer/Project Explorer". This aids the user when they wish to sort the classes in the project in that the classes are not interspersed with associations. This is a very common use-case for large model management.

This improvement to the the Simple UML Facet would be appreciated by most if not all users.

Comment 1 Eclipse Genie

2017-05-18 12:12:07 EDT

New Gerrit change created: https://git.eclipse.org/r/97472

Comment 2 Eclipse Genie

2017-11-06 10:26:08 EST

New Gerrit change created: https://git.eclipse.org/r/111065

Comment 3 Camille Letavernier

2017-11-06 10:38:51 EST

> New Gerrit change created: https://git.eclipse.org/r/111065

This is a first version of the contribution. I just realized that the "Link with Editor" in the ModelExplorer doesn't play well with Facets. Although the ContentProvider provides its own algorithm to reveal semantic elements (Taking customized references into account), it is wrapped in the CommonViewer / Common Navigation Framework, thus is not directly accessible. So the reveal algorithm is very generic and simply browses the containment tree up. As a result, it is only able to expand the tree up to the association's parent (The association itself is hidden behind a custom 'associations' reference).

As far as I can tell, there is not much we can do about this issue

There may potentially be other issues related to this patch: I'm not sure how many UML Elements may own references. I've identified Package#packagedElements, Class#nestedClassifiers and Interface#nestedClassifiers. If there are other options, associations will appear twice: once under the parent directly, and ane more time behind the "associations" custom reference.

Comment 4 Camille Letavernier

2017-11-06 10:45:31 EST

The issue I mentioned above is tracked in Bug 484648