Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354280 - Step must not be changed if an exception occurs while activating a wizard step
Summary: Step must not be changed if an exception occurs while activating a wizard step
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-09 12:56 EDT by Claudio Guglielmo CLA
Modified: 2015-07-06 08:24 EDT (History)
1 user (show)

See Also:


Attachments
Patch to resolve the bug (1.19 KB, patch)
2011-08-09 13:05 EDT, Claudio Guglielmo CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Claudio Guglielmo CLA 2011-08-09 12:56:24 EDT
Build Identifier: 3.7.0

I have a wizard with two steps. If the activation of step 2 generates an exception I would expect to still have step 1 as active step. This is not the case. IWizard#getActiveStep returns step 2 although it has not ben activated correctly.

Example scenario: Step 2 loads data, form of step 2 is not open yet. If I abort the data loading it generates an exception which is fine. Pressing next again leads to subsequent faults because there is an inconsistency which is bad.

Solution: Undo the step change if an exception occurs.

Reproducible: Always
Comment 1 Claudio Guglielmo CLA 2011-08-09 13:05:32 EDT
Created attachment 201162 [details]
Patch to resolve the bug
Comment 2 Andreas Hoegger CLA 2015-04-13 08:43:41 EDT
This ticket is obsolete and will be closed.
Comment 3 Matthias Zimmermann CLA 2015-07-06 08:24:46 EDT
bugzilla cleanup for bugs in state WONTFIX, INVALID and WORSFORME and no target milestone.

in case the bug should have been closed by mistake, please reopen the bug and let us know why you think that this bug should not have been closed.