I know what is it for. At least the first method. I'm wondering about the second method, which I suppose should be called endComponentRender (instead of beginComponentRender, which is there twice). I just don't understand what do you want to do in endComponentRender, assuming it's going to be called _after_ component is rendered. Because then you can't affect the rendered output (as it's alread written to the stream), you can only alter component instance or component tag (which I can't see a reason for, except maybe some kind of "monitoring")?
-Matej Juergen Donnerstag wrote: > Please look at one of the previous mail threads. It originated from > being able to make the wicket:message attribute more flexible (equal > to <wicket:message>). > > Juergen > > On 9/21/06, Matej Knopp <[EMAIL PROTECTED]> wrote: >> I like this. >> However, why is there beginComponentRender twice? >> I assume the later should be endComponentRender. So I also assume it >> would be called after the component was rendered, right? what do we need >> this for? It makes no sense to alter componentTag, does it? Or is this >> just for "monitoring" reasons? >> >> Anyway, I'm +1. >> >> -Matej >> >> Eelco Hillenius wrote: >>> Regarding the discussion here: >>> http://www.nabble.com/localized-attributes-tf2288202.html#a6393222 >>> >>> What do you think about an interface like IOnComponentRenderListener >>> >>> pulic interface IOnComponentRenderListener { >>> >>> void beginComponentRender(Component, ComponentTag) >>> >>> void beginComponentRender(Component, ComponentTag) >>> } >>> >>> Pro: it would make the wicket:message attribute possible, and would >>> open some more possibilities for AOP-ish constructs. >>> >>> Con: though I don't think we'd open up pandora's box, we are providing >>> a way for people to break encapsulation. >>> >>> You opinions or votes in case you're absolutely for or against? >>> >>> 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
