Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-beta-5
-
Fix Version/s: None
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Number of attachments :
Description
It seems kind of uncool for me, that ScriptedComposingLifecycleContainerBuilder instantializes builder map
in a static initalizer.
This way it introduces very miplicit dependency on groovy, javascript,
beanshel and whatever even if I'm not going to use those features....
And servlet stuff is not using this feature anyway, because real container composition if left to congigured ContainerComposer
( which would decide how to deal with configuration )
Activity
Aslak Hellesøy
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Aslak Hellesoy [ rinkrank ] |
Aslak Hellesøy
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Aslak Hellesøy
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
This is in progress (I have fixed it locally, will probably commit later today). There is similar functionality in the NanoContainer class. The entire logic will most likely move there.