Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by GregWoolsey: http://wiki.apache.org/tapestry/RecursiveComponents ------------------------------------------------------------------------------ I think this is really a bug with the `ForBean` class, but changing that would probably break something that was depending on it's current behavior, expecting to see the component or page property still referencing the last collection value after the `ForBean` was done rendering. + == Additional Problem with "If" Component == + If you want to enhance your recursive block with additional template logic, perhaps optionally rendering additional content for some iterations, you will want to use the `If` component. However, there is a bug in the template parsing code when it is used in this context. The condition binding is improperly cached between recursive calls, with the net result of the condition not being reevaluated for the first child iteration after the top-level call. + + The solution is to use a custom `.jwc` spec file, calling the component something else (I used "IfContext"). In this file, add the `cache="no"` attribute to the `condition` and `conditionValue` parameters to force Tapestry to evaluate their expressions on each access. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
