[jira] Updated: (RUNTIME-33) Document the collection policy for transient components.

[de...@avalon.apache.org]

The following issue has been updated:

    Updater: Stephen McConnell (mailto:mcconnell@apache.org)
       Date: Fri, 9 Jul 2004 11:16 AM
    Changes:
             Fix Version changed to 3.4.0
             Fix Version changed from 4.0
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/RUNTIME-33?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/RUNTIME-33

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: RUNTIME-33
    Summary: Document the collection policy for transient components.
       Type: Improvement

     Status: Open
   Priority: Minor

    Project: Merlin Runtime
 Components: 
             COMPOSITION
   Fix Fors:
             3.4.0
   Versions:
             4.0

   Assignee: Stephen McConnell
   Reporter: Stephen McConnell

    Created: Fri, 11 Jun 2004 7:10 AM
    Updated: Fri, 9 Jul 2004 11:16 AM

Description:
> "Stephen McConnell" <mc...@apache.org> schrieb im Newsbeitrag news:40C9B006.10805@apache.org...
> 
>>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!



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org