[nanocontainer-scm] [jira] Work Logged: (NANO-110) allow self-registration of container instance via script
jira-yCVjj/[email protected] Sat, 4 Dec 2004 15:02:21 -0500 (EST)
| Newsgroups | gmane.comp.java.nanocontainer.cvs |
|---|---|
| Message-ID | <[email protected]> |
The following work log has been added to this issue:
Logged By: Obie Fernandez
Created: Sat, 4 Dec 2004 3:01 PM
Time Logged: 8 hours
Description:
Some of this time was spent pairing with Aslak on fixing the infinite loop in the container lifecycle that resulted from being able to self-register.
---------------------------------------------------------------------
View this work log:
http://jira.codehaus.org/browse/NANO-110?page=worklog#action_27487
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/NANO-110
Here is an overview of the issue:
---------------------------------------------------------------------
Key: NANO-110
Summary: allow self-registration of container instance via script
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: 2 days
Time Spent: 8 hours
Remaining: 0 minutes
Project: NanoContainer
Components:
core
Assignee:
Reporter: Obie Fernandez
Created: Wed, 24 Nov 2004 11:13 AM
Updated: Sat, 4 Dec 2004 3:01 PM
Description:
As discussed with Aslak and Paul (11/23/2004)...
We agreed there are cases where it is desirable for PicoContainer to self-register itself and become available for injection into child components. The guard code that used to prevent this operation from being done manually has been removed by Paul (see PICO-226).
Instead of introducing a ContainerExposingPicoContainer into Pico and having to specify it as the container-implementation, we will add an optional register-self attribute to the scripting system. This attribute will cause nano to register the container within itself.
Example:
<container register-self=true>
<component-implementation class='org.nanocontainer.testmodel.DefaultWebServerConfig'/> ...
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira