tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-848) PropertyConduit instances should automatically disable when the underlying class loader is discarded (due to live class reloading)
Date Mon, 12 Jan 2015 08:11:06 GMT

     [ https://issues.apache.org/jira/browse/TAP5-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-848.
-------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> PropertyConduit instances should automatically disable when the underlying class loader
is discarded (due to live class reloading)
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-848
>                 URL: https://issues.apache.org/jira/browse/TAP5-848
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> This could be done using a PropertyConduit wrapper around the generated PC that was also
a listener for the appropriate notification from the correct  InvalidationEventHub. This would
help ensure that user code that directly makes use of PropertyConduits does not cause memory
leaks (i.e. leaking an entire class loader).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message