Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.2-RC1
-
Fix Version/s: 1.2
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Testcase included:yes
-
Number of attachments :
Description
If a DPC has a parent container, and component instantiation would cause a CyclicDE to be thrown, it is never thrown, and the component received 'null' instead.
Attached is a patch to fix this, but it breaks two tests:
DPCLifeCycleTestCase.testMaliciousComponentCannotExistInAChildContainerAndSeeAnyElementOfContainerHierarchy: It only returns "<One<Two"
DPCTestCase.testUpDownDependenciesCannotBeFollowed: It can't instantiate A because of unsatisfied dependencies
from what I can tell, the test behavior with this patch is still "ok", but would like others to review prior to commit.
Activity

Field | Original Value | New Value |
---|---|---|
Summary | CyclicDE never throw from DPC if a parent container exists | CyclicDE never thrown from DPC if a parent container exists |

Assignee | Aslak Hellesoy [ rinkrank ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Well, if it breaks those unit tests, it is not good. Personally I fear it is a consequence of
PICO-165...