Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370129 - [Core] ServicesRegistry should be accessible from any EObject attached to a Papyrus ResourceSet
Summary: [Core] ServicesRegistry should be accessible from any EObject attached to a P...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 0.9.0   Edit
Assignee: Cedric Dumoulin CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 359075
  Show dependency tree
 
Reported: 2012-01-30 09:37 EST by Cedric Dumoulin CLA
Modified: 2012-01-31 03:12 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Dumoulin CLA 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 CLA 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 CLA 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.