Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
class CompA {
ClassA(PicoContainer pc)
}
People with complex needs should explicitly place an (arbitary) PicoContainer into another via registerComponentInstance(..). I do this in Jesktop and EnterpriseObjectBroker and do not want hosted component makers to have a hook to my kernel.
I hope I do not have to explain this one ... It will take a long time.
Activity
Paul Hammant
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Paul Hammant [ paul ] |
Paul Hammant
made changes -
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Fix Version/s | 1.1 [ 10307 ] |
Aslak Hellesøy
made changes -
Status | Closed [ 6 ] | Reopened [ 4 ] |
Resolution | Fixed [ 1 ] |
Aslak Hellesøy
made changes -
Fix Version/s | 1.1 [ 10307 ] | |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Closed [ 6 ] |
Fix Version/s | 1.2 [ 11330 ] |
http://lists.codehaus.org/pipermail/picocontainer-dev/2004-April/003295.html
Is that close to what you mean?
I mean I aggree that it should be impossible (unless manually enabled) to get an instance of the hosting container in the ctor.