Bug 204549 - [ErrorHandling] Could StatusHandler call other status handler ?
Summary: [ErrorHandling] Could StatusHandler call other status handler ?
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-25 10:05 EDT by Christophe Elek CLA
Modified: 2019-09-06 16:18 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Elek CLA 2007-09-25 10:05:32 EDT
We need to test the following

Product A has a status handler
Product B installs itself in Product A and had a statusHandler
Can StatusHandler A discover statushandler B and call it ?
Comment 1 Krzysztof Daniel CLA 2008-10-13 04:40:52 EDT
I think this bug should be rather assigned to Kevin.

There are several questions:
(a) How do we decide which status handler is the basic one and which should be invoked first?
(b) What if every status handler displays a dialog? What if we have 100 status handlers?
(c) What if some of the status handlers do the same job?

Chris,
what is the use case?
Comment 2 Christophe Elek CLA 2008-10-14 08:44:32 EDT
Good point... ultimately here is what could-should happen

- the product has a company handler (i.e the company overrides anything the product can do). the company has the first look and decides what to do. If the company decides not to handle it, it 'passes' to the product handler

- the product handler is linked to the branding and if there is no company handler , handles the IStatus first. 

here is the dilemma is Product handler decides to 'not handle' the status
a) do we stop here ?
b) do we check if there is another 'branding' and we pass the status to the banding handler ?
c) do we call each plugin to see if they want to handle the IStatus ?


While I see value for #1 above, I am not sure there is demand for a,b or c..
I cced Jean Michel as he is working on Jazz and decided not to use the StatusHandler because of a similar issue... Jean-Michel, do you want to add to your use case ?
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:18: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.