Capella project explorer doesn't refresh new requirements after closing/reopening a session

[eclipse-capella-bot]

Capella 1.2.1 Requirements add-on 0.9.1

• create new capella project
• link it to the Capella Requirements VP (Viewpoint Manager)
• right-click the "Logical Architecture" folder, and use "add capella element" then "Capella Module"
• right-click the new module, "Add Capella Element", "Requirement"

The requirement appears in the tree (module is automatically expanded)

• right-click again and add another requirement

The requirement appears automatically without saving the model

• right-click the aird file and use "close"

session is closed, and the tree is automatically collapsed

• double click the aird file to reopen a session
• expand the tree down to the capella module
• right-click, add capella element, Requirement

If the module is not expanded beforehand, it is automatically expanded and the requirement appears. If the module had already been expanded, the requirement won't appear. Whatever the case, any subsequent requirement you try to add in that module will not appear in the tree.

After this, you can create another capella module wherever in the tree, add a new requirement to it : the first requirement will show automatically, but any subsequent ones won't (basically, only newly expanded modules will show a requirement)

This only fails for Requirements (at least, that's the only one I detected).

ECLIPSE-555386 POLARSYS-2182 @lgo 2018-09-12

[eclipse-capella-bot]

nle commented on 2018-09-18

It seems that org.polarsys.capella.vp.requirements.Requirements.provider.CapellaRequirementsItemProviderDecoratorAdapterFactory does not inherit from org.polarsys.capella.core.data.gen.edit.decorators.CustomDecoratorAdapterFactory that clears itemProviderDecorators cache correctly.

public void dispose() { super.dispose();

//[ECLIPSE-520102](https://github.com/search?q=ECLIPSE-520102&type=Issues)
itemProviderDecorators.clear();

... }

See patch in attachment.

nle commented on 2018-09-18

Attachment: 2182.patch OutOfMemoryError in Synchronizer.runAsyncMessages

lgo commented on 2018-09-24

The same bug happens when closing and reopening the capella model explorer instead of closing and reopening a session. The root cause is likely the same.