Bug 544 - One byte error causes entire project to be discarded without error.
Summary: One byte error causes entire project to be discarded without error.
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 : Enhancement (vote)
Target Milestone: 1.0 M3
Assignee: Will Peterson
QA Contact: Stephen Harmon
URL:
Whiteboard:
Keywords: Built, Provo
Depends on:
Blocks:
 
Reported: 2004-12-10 18:58 UTC by Bill Street
Modified: 2011-06-04 04:17 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 Bill Street 2004-12-10 18:58:19 UTC 
DETAILED DESCRIPTION: from DRFOSTER:
I had a 2+ megabyte .proj file.  I edited it and introduced a 1 byte error that
caused the XML to be invalid.  I started Designer with this as my default
project.  No error was displayed and nothing with displayed by the modeler in my
project although it had numerous objects in it.  I shut down Designer.  My .proj
file was reduced to 400+ bytes that represented a simple empty project.  I never
said save yet my .proj file was re-written.  EVERYTHING I had in my project was
discarded.  This is unacceptable.  We should detect errors in the XML and tell
the user, not blow away the project.


BUILD NUMBER: 
Oses/CONFIG: 
STEPS TO REPRO: 
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 Will Peterson 2004-12-10 20:47:03 UTC 
I talked with Dennis about this (originator of the defect), He simply wants the
model to be able to recognize invalid prortions of the model (when a file is
corrupted) and give handles to the developers (or prompt the user) that the file
is not well formed  ... or is otherwise invalid.
Comment 2 Will Peterson 2004-12-13 20:57:27 UTC 
I have reviewed defect with Dennis.  The more recent model does not have this
behavior, however I am leaving it open to investigate an interesting thing we found:

- changing or removing the closing tag on an XMI file has no effect on loading
(and we'ere wonding if it should since the file would no longer be well-formed)
 My guess is that they have an optimization turned on (for loading).
Comment 3 Will Peterson 2005-01-24 22:29:37 UTC 
This behavior in he last comment does not seem to cause any problems after going
through some tests.  I belive it is just fault tolerance of EMF
Comment 4 Howard Vanfleet 2005-01-25 00:36:29 UTC 
Included in Designer build 20050124
Comment 5 Howard Vanfleet 2005-01-25 22:03:11 UTC 
Included in Designer build 20050125
Comment 6 Stephen Harmon 2005-01-27 16:30:33 UTC 
Regressed 0126
Comment 7 Bill Street 2005-09-16 21:31:11 UTC 
Adding built keyword.
Comment 8 Bill Street 2007-04-30 16:37:11 UTC 
Marking closed/resolved fixed bugs public view.
Comment 9 Bill Street 2007-04-30 16:39:42 UTC 
Marking closed/resolved fixed bugs public view.