Bug 412322 - [DI] Release ExtendedObjectSupplier as API for Eclipse 4.4
Summary: [DI] Release ExtendedObjectSupplier as API for Eclipse 4.4
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 4.4   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Paul Elder CLA
URL:
Whiteboard:
Keywords: api
Depends on: 413147
Blocks: 412373
  Show dependency tree
 
Reported: 2013-07-04 10:28 EDT by Lars Vogel CLA
Modified: 2014-04-28 14:05 EDT (History)
5 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 Lars Vogel CLA 2013-07-04 10:28:06 EDT 
ExtendedObjectSupplier is currently not released as API. Maybe we can do this for Eclipse 4.4?
Comment 1 Thomas Schindl CLA 2014-02-23 02:37:32 EST 
IMHO one of the major flaws in the ExtendedObjectSupplier system is that it uses Injection using the static InjectorFactory.getDefault().

This a real problem if you e.g. look at UIEventObjectSupplier which accesses UISynchronize from there - looking into the future this won't work for multi-user envs.

It's not per se wrong to use DI but too me it looks strange that something that is an OSGi-Service holds DI stuff. We need at least document clearly how DI works in this context and have to provide a guaranteed way to replace object suppliers using service.ranking - see bug 428837
Comment 2 Lars Vogel CLA 2014-04-28 14:05:15 EDT 
Marking as WONTFIX for Luna, we can decide again for Mars.