Bug 3038 - Registry caching has no error checking (1GELYDT)
Summary: Registry caching has no error checking (1GELYDT)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 F1   Edit
Assignee: Debbie Wilson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:48 EDT by Debbie Wilson CLA
Modified: 2002-05-23 11:07 EDT (History)
0 users

See Also:

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 Debbie Wilson CLA 2001-10-10 22:48:16 EDT 
The classes RegistryCacheReader and RegistryCacheWriter which read and write the
plugin registry to a cache file, respectively, do not have any error checking.  They do
not pass a status back to indicate a failure.  As a result, a failure could occur leaving
a corrupt plugin registry without anyone knowing about it.

NOTES:

JM (6/5/2001 9:57:42 PM)
	Defer
Comment 1 Debbie Wilson CLA 2002-02-12 14:40:19 EST 
Registry caching will now fail if an unexpected byte code is encountered.  In 
this case, a null registry is returned.  It is assumed that the cache is 
corrupt so the entire registry will need to be re-read.
Comment 2 DJ Houghton CLA 2002-05-23 11:07:34 EDT 
Fixed.