[ https://issues.apache.org/jira/browse/TAP5-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869587#action_12869587 ]
Seth Call edited comment on TAP5-857 at 5/20/10 8:42 AM: --------------------------------------------------------- We have a component which allows us to render components that derive from a certain base class: http://blog.bolkey.com/2009/06/tapestry-5-recursive-tree/ IT allows us to render trees coming from our database, essentially. Very useful. Then, we made the tree editable on the web page; we do an ajax update, and then the partial re-render upsets tapestry with recursion detection. So in the end, the problem for us has been that it's very difficult to have a tree-like business model with tapestry. Not without jumping through quite a few hoops. was (Author: ownedthx): We have a component which allows us to test components that derive from a certain base class: http://blog.bolkey.com/2009/06/tapestry-5-recursive-tree/ IT allows us to render trees coming from our database, essentially. Very useful. Then, we made the tree editable on the web page; we do an ajax update, and then the partial re-render upsets tapestry with recursion detection. So in the end, the problem for us has been that it's very difficult to have a tree-like business model with tapestry. Not without jumping through quite a few hoops. > 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.