Ahh, I should have read it more carefully. But I still don't like to basically disable all tests for children of <wicket:head> containers. Can't we either mark them as being rendered if the flag is true or change the use check in a way that it only ignores head child if head-flag is true.
Juergen On 9/26/06, Matej Knopp <[EMAIL PROTECTED]> wrote: > If we do that we can as well as remove the flag completely, because it > would rendere it useless then. > > The flags purpose is to prevent writing header contribution to ajax > response for components, whose header contribution has already been made > (so that we reduce the size of ajax response). > > The flag is cleared on each "regular" request, which is all right. > > -Matej > > Juergen Donnerstag wrote: > > Not sure. Why not reset the flag of all children at the beginning of > > each render cycle. I remember we did that some time before. > > > > Juergen > > > > On 9/26/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > >> On 9/26/06, Matej Knopp <[EMAIL PROTECTED]> wrote: > >>> There's a problem with panel that have components in wicket:head and are > >>> rendered using ajax. > >>> > >>> The problem is that first time, the wicket:head is rendered. But any > >>> subsequent call to component.renderHead() is ignored, because the head > >>> has already been rendered (the state of rendering head is stored as > >>> component flag). So every subsequent call to component.render will fail, > >>> because components placed to wicket:head will not be rendered. What can > >>> we do about this? > >>> Wouldn't it be best just to ignore component use check for components > >>> that are in <wicket:head>? > >> Sounds good to me. > >> > >> Eelco > >> > >> ------------------------------------------------------------------------- > >> Take Surveys. Earn Cash. Influence the Future of IT > >> Join SourceForge.net's Techsay panel and you'll get the chance to share > >> your > >> opinions on IT & business topics through brief surveys -- and earn cash > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> _______________________________________________ > >> Wicket-develop mailing list > >> Wicket-develop@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wicket-develop > >> > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys -- and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Wicket-develop mailing list > > Wicket-develop@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wicket-develop mailing list > Wicket-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
