Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 1.2
-
Fix Version/s: 1.2
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Environment:JDK 1.5, WinXP
-
Testcase included:yes
-
Number of attachments :
Description
Below is a blatant disregard of PicoContainer APIs. However, Visiting doesn't allow you to uncover the real culprit because an NPE is thrown. I'd really like to see it 'fixed' enough so taht VerifyingVisitor can catch the error and thereby print out something useful instead.
(Note, this NPE will occur on any visitor, not just a VerifyingVisitor)
public void testBlowUpPicoVisitorWithNullParameter() throws NullPointerException {
MutablePicoContainer picoToMuckWith = new DefaultPicoContainer();
picoToMuckWith.registerComponent(new ConstructorInjectionComponentAdapter(ArrayList.class, ArrayList.class,
new Parameter[3]));
VerifyingVisitor vv = new VerifyingVisitor();
//Will throw NPE when visiting the component adapter.
vv.traverse(picoToMuckWith);
}
Thanks!
-Mike (R)
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Joerg Schaible [ joehni ] |
Fix Version/s | 1.3 [ 11331 ] |
Fix Version/s | 1.2 [ 11330 ] | |
Fix Version/s | 1.3 [ 11331 ] |
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
We follow the fail-fast rule. Therefore is now a NPE thrown creating the CA.