[
https://issues.apache.org/jira/browse/TAP5-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869601#action_12869601
]
Seth Call commented on TAP5-857:
--------------------------------
The problem is, we have a top level component that's a TreeRenderer. So
it's not the individual tree nodes causing the problem, it's the fact that I
need to use this component to render the initial tree, and then use it again
to re-render a part of the tree during ajax. But, I have to place this
TreeRenderer inside of itself to pull this off; causing the recursion.
But it wil never actually recurse, because it's happening in a ajax-only
zone.
Anyway, I understand it's a lot of code to change for this particular
usecase; I've looked at it before. But I'm telling you boy did we have alot
of hoops to jump through to do this.
On Thu, May 20, 2010 at 8:21 AM, Thiago H. de Paula Figueiredo (JIRA) <
> 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.
