[jira] [Closed] (TAP5-857) Exclude recursion detection during initial render on blocks that are used for zone updates.

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade closed TAP5-857.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Exclude recursion detection during initial render on blocks that are used for zone updates.
> -------------------------------------------------------------------------------------------
>
>                 Key: TAP5-857
>                 URL: https://issues.apache.org/jira/browse/TAP5-857
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1
>            Reporter: Seth Call
>              Labels: bulk-close-candidate
>
> Currently it is not possible to define a t:block that uses a particular component when that component is already above in the hierarchy, because Tapestry will detect this as a recursion.
> However, if this recursion-causing block is only to be used as responses to a zone update, then ideally it wouldn't cause a recursion to be detected.  
> Say for instance this were possible:
> <t:zoneBlock>
>    ...
> <t:zoneBlock>
> Where t:zoneBlock is identical to t:block except it can only be used as the response to a zone update, and assembly of the page would know to exclude the contents of that block when it's a normal full page render to avoid the initial reason the recursion detection was added in the first place (runaway rendering issues).



--
This message was sent by Atlassian JIRA
(v6.2#6252)