I've tested the patch and can confirm that it doesn't break existing code. I agree with you that extended AttributeModier by means of "Behaviours" to allow for more general use may open up new possibilities / solutions to unsolved problems. What I not yet understood, why is this a better approach compared to extending one of existing components and implementing the extensions by means of the existing hooks?
Juergen On 11/6/05, Ralf Ebert <[EMAIL PROTECTED]> wrote: > Hi, > > > Make a RFE for this and attach youre patch. > well, I thought of this more as an idea for discussion then as a > concrete request for enhancement, the patch was just for trying out > if that works well together with concepts which are already there. > But as requested I filed an RFE for this. > > Regards, > Ralf > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
