Bug 291640 - New unchecked coreexception or interface for IStatus-based exceptions
Summary: New unchecked coreexception or interface for IStatus-based exceptions
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-07 13:32 EDT by Min Idzelis CLA
Modified: 2019-09-06 16:08 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Min Idzelis CLA 2009-10-07 13:32:52 EDT
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: 

Currently, the platform only has 1 IStatus based exception (CoreException). These are nice, since they can hold a hierarchy of child exceptions, and they are all properly logged to the error log. 

However, one limitation is that CoreException is a checked exception, which means that it cannot be used in some circumstances. 

I have created my own unchecked Runtime exception that contains an IStatus object. However, because the Eclipse platform logger (PlatformLogWriter) does not know that my custom exception contains a nested IStatus, it does not log these errors causing missing information in the log. 

I propose that we add support for this scenerio. There are 2 ways I can think off of the top of my head, either (or both) will work. 

1) Create an interface for the PlatformLogWriter to query instead of CoreException. (IStatusBasedException?) 
2) Create an unchecked version of CoreException that I can subclass or use directly. (CoreRuntimeException?) 


Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:08:37 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.