Bug 482 - HandleActivateDiscard is not being called when the editor is dirty
Summary: HandleActivateDiscard is not being called when the editor is dirty
Status: VERIFIED FIXED
Alias: None
Product: Identity Designer
Classification: Identity Manager
Component: Project Model (show other bugs)
Version: 1.0.0 Designer
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: 1.0 M2
Assignee: Will Peterson
QA Contact: Tim Pew
URL:
Whiteboard:
Keywords: Built, Provo
Depends on:
Blocks:
 
Reported: 2004-12-09 22:30 UTC by Brent Thurgood
Modified: 2011-06-04 16:21 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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 Brent Thurgood 2004-12-09 22:30:15 UTC 
DETAILED DESCRIPTION:
HandleActivateDiscard is not being called when the 
editor is dirty this does not allow the policy 
editor to close when it's parent is deleted. This is 
because HandleActivateDiscard is not called if the 
isDirty flag is true. We should call 
HandleActivateDiscard regardless of whether or not 
we are dirty if one of the removed resources is our 
input resource or any of it's parent resources.

BUILD NUMBER: 

Oses/CONFIG: 

STEPS TO REPRO: 

1. Create and save a policy in the Driver Editor
2. Lauch the policy editor and modify the policy 
without saving
3. Return to the Driver Editor and delete the policy
4. Save the Driver Editor


RESULTS:

EXPECTED: 

WORKAROUNDS: 

CUSTOMER IMPACT: 


NTS entered defects should also include:
Additional debug info like screenshots, screencams, 
log files, trace files,
packet traces, memory coredump location.
Accurate customer information so that proper 
prioritizing of the defect is
possible (mainly for NTS defects)
Comment 1 Lee Lowry 2004-12-13 20:20:17 UTC 
This has nothing to do with the Modeler code - it's just the 
interaction between two Policy Editors and the problem is in 
DesignerMultiPageEditorPart Line #210.
Comment 2 Will Peterson 2004-12-13 23:56:08 UTC 
I just went over this with ryan, i'm going to up the priority.

Basically, instead of just checking for !isDirty() we need a check that is more
like (!isDirty() || isRootObject()) -> then go ahead and close the editor (or
possibly call HandleActivateDiscard ... but prob. just leave it seperate)
Comment 3 Will Peterson 2005-01-07 16:01:33 UTC 
This has been fixed.  I tested it with the current build.
Comment 4 Howard Vanfleet 2005-01-07 17:52:39 UTC 
Included in Designer build 20050107
Comment 5 Bill Street 2005-09-16 21:31:49 UTC 
Adding built keyword.
Comment 6 Bill Street 2007-04-30 16:36:59 UTC 
Marking closed/resolved fixed bugs public view.
Comment 7 Bill Street 2007-04-30 16:39:21 UTC 
Marking closed/resolved fixed bugs public view.