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

Bug 415588

Summary:	[Resource Loading] Load/unload actions for controlled units do not appear in the Model Explorer
Product:	[Modeling] Papyrus	Reporter:	Christian Damus <give.a.damus>
Component:	Core	Assignee:	Christian Damus <give.a.damus>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P2	CC:	mathieu.velten, pierre-charles.david
Version:	0.10.0	Flags:	give.a.damus: kepler+
Target Milestone:	SR1
Hardware:	PC
OS:	Mac OS X
URL:	http://www.eclipse.org/forums/index.php/t/508834/
Whiteboard:
Bug Depends on:
Bug Blocks:	415369

Description Christian Damus

2013-08-21 10:07:30 EDT

Papyrus Git master updated to 20 August 2013 on a Kepler SR0 target.

The actions for loading and unloading controlled resources do not appear in the Model Explorer view.  This could be a problem in their visibility expressions, which use 'isAllLoaded' and 'isAllNotLoaded' property testers that target the IStructuredSelection type instead of some model type (possibly by adaptation) such as EObject.

Comment 1 Christian Damus

2013-08-21 16:54:27 EDT

Re-targeting for Kepler SR1 as the controlled resource feature (even in the workspace) is quite broken without these menu actions.

Comment 2 Christian Damus

2013-08-21 17:01:16 EDT

Fixed in Kepler SR1.

Commit b21bb237dedca6ec253571b6e9b0448477e4d236

The problem turned out to be simply that references to the loaded/unloaded controlled unit property testers were using the wrong property namespace.  It seems that a renaming of the oep.infra.core.resourceloading plug-in ID as oep.infra.services.resourceloading was applied to references to the property testers in the diagram and model-explorer plug-ins, but the property tester namespace was actually still oep.infra.core.resourceloading.tester (based on the former plug-in ID).

The safe fix for SR1 was to update the references to use the actual property tester namespace, even though it seems "wrong" (not matching the defining plug-in's namespace).  This is not really a problem, because property tester namespaces have no relation to plug-in IDs.  Changing the property tester namespace declaration could have broken other references that I don't know about; if somebody wants to do that in the Luna release, fine.