Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339200 - Parts that could not be created needs to show the user an error occurred
Summary: Parts that could not be created needs to show the user an error occurred
Status: RESOLVED WORKSFORME
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 07:09 EST by Remy Suen CLA
Modified: 2019-09-02 15:02 EDT (History)
0 users

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 Remy Suen CLA 2011-03-08 07:09:30 EST 
We have error parts in the compatibility layer but we need something similar for 4.x parts. Also, the compatibility layer's protection mechanism only guards against failures that occur in the client's code. If our underlying implementations fail then the part will still be empty. We need to craft something for use by the ContributedPartRenderer directly.

One option we could pursue is to extract StatusPart and then port it over to 4.x.
Comment 1 Eclipse Genie CLA 2019-05-29 12:48:34 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Lars Vogel CLA 2019-09-02 15:02:14 EDT 
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.