[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Extension registry evolution

Oleg,

Great to see typed objects moving into the extension registry! 
I am not sure if I fully understand IRegistryObject, therefore the following might not apply: I would not like my classes having to implement this platform related interface. Better provide an (additional) reflection based approach here in order to be non-invasive (e.g. like Spring DI).

What I really would love to see is the extension registry being based on or supporting the OSGi programming model. It is hard to have two similar approaches around and having to know both. Why not let the extension registry be an OSGi service (de)populated by applying the extender pattern? Then listening to changes in the registry (e.g. some new menu items coming in with a new bundle) would be the same task like listening to any OSGi service changes.

Cheers
Heiko

Am 24.09.2008 um 21:19 schrieb Oleg Besedin:


What would you like to see in the extension registry 2010?

If you have an opinion on how the extension registry can be improved, please visit:

        http://wiki.eclipse.org/Equinox_Extension_Registry_Work

        https://bugs.eclipse.org/bugs/show_bug.cgi?id=248340

and leave your comments!

So far we have identified several potential areas:

- Create typed Java objects instead of forcing you to crawl through IConfigurationElements  (see http://wiki.eclipse.org/Equinox_Extension_Registry_Work_Objects for details)
- Expand ability to programmatically modify extension registry
- Add support for non-singleton bundles

Does it sound like something you'd like to see in Eclipse?

(Please use this mailing list for general discussions and bug / wiki for more detailed comments.)

Thanks,
Oleg
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev