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

Bug 370129

Summary:	[Core] ServicesRegistry should be accessible from any EObject attached to a Papyrus ResourceSet
Product:	[Modeling] Papyrus	Reporter:	Cedric Dumoulin <cedric.dumoulin>
Component:	Core	Assignee:	Cedric Dumoulin <cedric.dumoulin>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	cedric.dumoulin, cletavernier, faure.tristan
Version:	0.9.0
Target Milestone:	0.9.0
Hardware:	PC
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	359075

Description Cedric Dumoulin

2012-01-30 09:37:52 EST

The ServicesRegistry should be accessible from any EObject attached to a Papyrus ResourceSet.

Nearly all services and code of Papyrus act on the models representing the uml model.
Models are actually implemented with emf Resource and ResourceSet. Each uml model, and each Papyrus editor, has its own ResourceSet.

It could be interesting to be able to get the Papyrus ServicesRegistry from an EObject attached to a ResourceSet.

Comment 1 Cedric Dumoulin

2012-01-30 10:39:01 EST

The new class ServiceUtilsForResource is added.
It allows to find the ServiceRegistry from an EObject.
See also the wiki.

Comment 2 Camille Letavernier

2012-01-31 03:12:55 EST

An export package were removed from infra.emf Manifest during your last change, which broke the build.

I've added it again in r7075.