Summary: | Need ability to extend ElementSelectionService for transaction support | ||||||
---|---|---|---|---|---|---|---|
Product: | [Modeling] GMF-Runtime | Reporter: | Christian Damus <give.a.damus> | ||||
Component: | General | Assignee: | Anthony Hunter <ahunter.eclipse> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | major | ||||||
Priority: | P3 | Keywords: | contributed | ||||
Version: | 1.0 | ||||||
Target Milestone: | 1.0.1 | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Christian Damus
2006-06-23 14:11:41 EDT
Created attachment 45195 [details]
Patch for selection service extensibility
As promised, find attached a patch that makes the following small changes:
- in ElementSelectionService and AbstractElementSelectionProvider,
factors out the creation of ElementSelectionServiceJobs to allow a
subclass to create a custom job implementation
- in ElementSelectionService, factors out the scheduling of jobs so that
a subclass can customize the scheduling of provider jobs
- in ElementSelectionComposite, adds a constructor that allows clients
to configure the composite with a custom selection service implementation
Committed the patch to R1_0_maintenance. I ran the JUnit tests for the element selection service and they pass. I also ran the clients application and it works as required. [GMF Restructure] Bug 319140 : product GMF and component Runtime Common was the original product and component for this bug |