This is normal. There are most specific methods that get called in the lifecycle of the individual component.
pageBeginRender() means the Page is beginning to render, long before any of the components render. On 10/1/07, sunilmanu <[EMAIL PROTECTED]> wrote: > > > Hello Everyone, > > We are using Tapestry 4.0.2 . Recently we noticed a following issue : > > We have a HTML page that has multiple COMPONENTS but are in IF conditional > block. No matter how the condition is evaluated to TRUE /FALSE, the > Components are getting called i.e. the PAGEBEGINRENDER method is being > called eventhough they are NOT rendered !! > > HTML > ===== > > > > > > > > > > > > In the above piece, it renders properly in the browser but the > PAGEBEGINRENDER method is fired 3 times even if the Condition is FALSE. > > We can definitely pass one more parameter to the component telling it > whether to process the iteration or not but is there a better way to > handle > this unwanted Component initialization ?? > > Thanks, > Sunil > > -- > View this message in context: > http://www.nabble.com/T4%3A-Components-in-Page-get-Initialized-even-if-its-in-IF-condition-block---tf4550131.html#a12984881 > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind
