On Sun, 2 Jan 2005 19:02:42 +0100, Juergen Donnerstag wrote:
>That sounds like good idea. you actually don't need such a remover.
>You may replace handleComponentTag and renderBody an write an empty
>string. Not sure I got the methodnames right though.
Actually, I like this approach even better. That is, instead of
having a ComponentTagRemover and ComponentTagAttributeModifier, why
don't we just invoke callback methods and allow the user to handle all
this logic? I think it is even more flexible this way.
Gili
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
