Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316462 - [sfs] improve robustness and error handling when content provider cann't be found or created
Summary: [sfs] improve robustness and error handling when content provider cann't be f...
Status: RESOLVED FIXED
Alias: None
Product: e4
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eduard Bartsch CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 09:50 EDT by Eduard Bartsch CLA
Modified: 2010-09-20 11:28 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eduard Bartsch CLA 2010-06-10 09:50:41 EDT
Currently, a method IFileStore.childStores() throws an exception when a content provider cann't be found or created for at least one file store. IFileStore.getChild() also throws an exception in this situation. This is problematic because the whole SFS subtree cann't be accessed anymore. It is also not possible to delete the corrupted content only that sometimes leads to a situation when the whole workspace has to be recreated. 

The fix should handle both aspects:
- The methods IFileStore.childStores() and IFileStore.getChild() should return the file store(s) but subsequently all methods of semantic file store that involve a content provider should throw an exception.
- A force removal methods and UI actions should be implementd to allow dedicated repair operations that forcefully remove corrupted content.
Comment 1 Eduard Bartsch CLA 2010-06-15 11:21:16 EDT
Implementation is checked in into CVS
Comment 2 Eduard Bartsch CLA 2010-09-20 11:28:59 EDT
Changes are released with v20100819-1010