Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341015

Summary:	RegionSpanningException and IndeterminateRegionException are dead code and should be deleted
Product:	[RT] Virgo	Reporter:	Glyn Normington <glyn.normington>
Component:	runtime	Assignee:	Project Inbox <virgo-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	tjwatson
Version:	unspecified
Target Milestone:	3.0.0.M04
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Glyn Normington

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.