[
https://issues.apache.org/jira/browse/TAP5-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313844#comment-14313844
]
Hudson commented on TAP5-2445:
------------------------------
FAILURE: Integrated in tapestry-trunk-freestyle #1380 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1380/])
TAP5-2450, TAP5-2445: Reset the renderTag field in the AfterRender phase, fixes
state leak when using an AbstractConditional within a Loop (jochen.kemnade: rev
69a689d45055c1c4fae7a1fcf53422052cfca890)
*
tapestry-core/src/test/resources/org/apache/tapestry5/integration/app2/pages/TestPageForIf.tml
*
tapestry-core/src/test/java/org/apache/tapestry5/integration/pagelevel/IfTest.java
*
tapestry-core/src/main/java/org/apache/tapestry5/corelib/base/AbstractConditional.java
> Reduce usage of PerthreadMap in AbstractConditional
> ---------------------------------------------------
>
> Key: TAP5-2445
> URL: https://issues.apache.org/jira/browse/TAP5-2445
> Project: Tapestry 5
> Issue Type: Sub-task
> Components: tapestry-core
> Reporter: Michael Mikhulya
> Assignee: Jochen Kemnade
> Priority: Minor
> Labels: patch, performance
> Fix For: 5.4
>
> Attachments: 0001-Reduce-usage-of-PerthreadMap.patch
>
>
> Probably this patch is curious to those who is not familiar with tapestry
> internals.
> It reduces number of accesses to PerthreadMap from 2 to 1 or 0 for each
> beginRender call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
