Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341015 - RegionSpanningException and IndeterminateRegionException are dead code and should be deleted
Summary: RegionSpanningException and IndeterminateRegionException are dead code and sh...
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.0.0.M04   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-25 17:48 EDT by Glyn Normington CLA
Modified: 2011-03-29 05:08 EDT (History)
1 user (show)

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 Glyn Normington CLA 2011-03-25 17:48:42 EDT 
This was spotted by Tom Watson.

RegionSpanningException is a throwback to when we allowed bundles, particularly the system bundle, to belong to more than one region. This was a really bad idea and is no longer allowed. So the exception should be deleted.

IndeterminateRegionException was only used when querying the region of a bundle using RegionDigraph. But now we return null instead of throwing an exception. Given the way we inherit the regions if BundleContext.installBundle is used outside the context of the digraph code, this is less of an issue. Once the digraph is set up, bundles will naturally be assigned a region as they are created. Again this exception should be deleted.