533139 – E4Application: Ensure start of org.eclipse.e4.ui.services

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

Bug 533139 - E4Application: Ensure start of org.eclipse.e4.ui.services

Summary: E4Application: Ensure start of org.eclipse.e4.ui.services

Status:	CLOSED DUPLICATE of bug 512052

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	4.8
Hardware:	All All

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	Platform-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2018-04-02 09:26 EDT by Karsten Thoms
Modified:	2018-04-02 10:32 EDT (History)
CC List:	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 Karsten Thoms

2018-04-02 09:26:18 EDT

I am often facing problems starting a workbench when 
   org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext()
is called on startup and ModelServiceImpl is created. The failure is that an instance of IEventBroker can't be retrieved from the appContext.

Responsible for providing IEventBroker is bundle org.eclipse.e4.ui.services. When this bundle was not started before execution of E4Application#createE4Workbench(), then the retrieval of IEventBroker fails and the application does not start.

The problem is how to enforce that? In PDE, I just created a default Eclipse launch configuration, and pointed the workspace to an existing one. All plugins are started by default, no special order given. Is it in responsibility of PDE to ensure that org.eclipse.e4.ui.services is started? Or is it valid to enforce the start when E4Application#createE4Workbench() is called (a bundle requirement already exists, so we can be sure that this bundle is on platform).

Comment 1 Andrey Loskutov

2018-04-02 10:32:23 EDT

Karsten, I believe this is a dup of bug 512052.

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