[
https://issues.apache.org/jira/browse/TAP5-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869598#action_12869598
]
Thiago H. de Paula Figueiredo commented on TAP5-857:
----------------------------------------------------
Page, components and templates int Tapestry have static structure.The recursion
check can't be removed because it prevents infinite loops to happen.
Instead of using recursion in the template, do that in the component class
using methods that handle the rendering events.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
