[RUNTIME-33] Document the collection policy for transient components.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 3.4.0
• Component/s: COMPOSITION
• Assignee: Stephen McConnell
• Reporter: Stephen McConnell
• Created: 11/Jun/04 14:10
• Updated: 13/Nov/04 02:13
• Resolved: 13/Nov/04 02:13

Description

> "Stephen McConnell" <[e-mail]> schrieb im Newsbeitrag news:[e-mail]...
>
>>Eike Stepper wrote:
>>
>>
>>>i solved it:
>>>
>>>i did the registration of the component from within the
>>>component code so that the registry had a handle to the component.
>>>now i do the registration from outside and a handle to the proxy
>>>is stored in the map and abracadabra: the proxy is no longer
>>>garbage collected ))
>>
>>Was about to suggest this - basically the container cannot hold a hard
>>reference to a transient component because this would result in a direct
>>memory leak. Transients are a special case that default to a non-hard
>>collection policy. As you discovered - if you maintain a reference to
>>the component then the component will not be garbage collected.
>
>
> such kind of special treatment should really be mentioned in the docs
> and your last sentence is misleading: obviously holding a handle to the
> component does not prevent the proxy from being finalized. in my opinion
> it's most important to state that the proxy must be strongly reachable!