Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354198 - Generalize services infrastructure
Summary: Generalize services infrastructure
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Konstantin Komissarchik CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2011-08-08 19:05 EDT by Konstantin Komissarchik CLA
Modified: 2021-11-19 09:21 EST (History)
1 user (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 Konstantin Komissarchik CLA 2011-08-08 19:05:10 EDT 
Sapphire services infrastructure is specific to element instance and property instance contexts. Extending the infrastructure to use services in other contexts is costly and the cost needs to be repeated for every new context. 

The services infrastructure should be re-visited to make it more generic. It should be fairly cheap to define a new context for services.
Comment 1 Konstantin Komissarchik CLA 2011-08-08 19:11:29 EDT 
Done.

ModelElementService and ModelPropertyService classes have been collapsed into a single Service class. Similarly, the manner in which services are registered in sapphire-extension.xml has been consolidated into a single construct. The new construct has a new required element called context, which identifies the context to which the defined service is applicable to. The new ServiceContext will make it easier to use services in other contexts.

See the migration guide under Services for more detail on the changes.
Comment 2 Shenxue Zhou CLA 2011-11-28 18:41:41 EST 
Verified the unified Service infrastructure.