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

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 5.1
• Component/s: tapestry-core
• Labels: bulk-close-candidate
• Assignee: Unassigned
• Reporter: Seth Call
• Created: 21/Sep/09 15:33
• Updated: 13/May/14 13:22
• Resolved: 13/May/14 13:22

Description

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).