[
https://issues.apache.org/jira/browse/TAP5-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-848:
--------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated about 1.5 years ago, has no assignee, affects
an old version of Tapestry that is not actively developed anymore, and is
therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry (5.4-beta-6, which is available from Maven Central), please update it
as soon as possible. In the case of a feature request, please discuss it with
the Tapestry developer community on the [email protected] mailing list
first.
> 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.2#6252)
