Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.0-beta-5
-
Fix Version/s: None
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Number of attachments :
Description
ServletContainerListener (line 52) does
containerBuilder.buildContainer(containerRef, null, context);
But LifeCycleContainerBuilder.buildContainer(containerRef, parentContainerRef, context) does
parentContainerRef.get();
on line 24. So in its current state, an NPE is thrown when the ServletContext is initialised.
I think a simple null check in LifeCycleContainerBuilder.buildContainer is the way to go. See patch.
Activity

Field | Original Value | New Value |
---|---|---|
Attachment | nullCheck.patch.txt [ 11419 ] |

Assignee | Aslak Hellesoy [ rinkrank ] | |
Resolution | Won't Fix [ 2 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
patch to check for null parent container reference. we should be able to instantiate a container given a null parent container reference (especially as the servlet code tries to do just that!)