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

Bug 193550

Summary: Extensions Registry Notifications ver.2
Product: [Eclipse Project] Equinox Reporter: Oleg Besedin <ob1.eclipse>
Component: CompendiumAssignee: equinox.compendium-inbox <equinox.compendium-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Oleg Besedin CLA 2007-06-20 11:38:58 EDT 
The registry notification mechanism needs to be improved. The known issues include:

- From the delta it is impossible to see if extension or extension point is affected
- A single registry change produces multiple deltas that individually don’t show complete picture of the change
 - Linking between extension points and extensions being modified is inconsistent
- There is no clear understanding how far previous registry state is preserved (i.e., if another extension is modified between the initial registry change should this change be present or absent)

The registry notifications have an inherent contradiction between been asynchronous and expected to provide a lot of data that corresponds to some past registry state.

The proposal of this enhancement is to provide a new registry notifications that would contain the list of extensions and extension points being modified. Notification will include only IDs of the extensions/extensions points being modified.
Comment 1 Oleg Besedin CLA 2007-10-19 15:04:06 EDT 
I created bug 206936 instead - after more research done the description above is not quite accurate. I really wish Bugzilla allowed editing of comments.


*** This bug has been marked as a duplicate of bug 206936 ***