Why do request handler need to be more intelligent than existing event handlers - they are doing exactly the same thing: reacting to events. Where the added complexity comes in is in the model objects as these need someone waht to support change detection.
If rendering would not change, and would thus still be the responsibility of the component, it wouldn't be the problem I meant.
Yes, we must only have one component tree. However, what we need to do is AJAX enable the existing components rather than have AJAX alternatives.
Not sure if I understand what you mean. Why I think it is usefull to be able to attach ajax handlers to components instead of building it in, is that it is a matter of combining. E.g. in one case, you like to check the validity of a TextField on an onchange, but in another case, you might want to do a lookup of and render another component (like an address lookup) on TextField's onchange. So the components stay the same, but the wanted ajax behaviour can vary.
Cheers, Eelco ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
