On Tue, Aug 17, 2010 at 7:02 AM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote:
> In case of wiQuery, many behaviors wicket AJAX is used (not jquery > AJAX) so it seem natural to use AbstractDefaultAjaxBehavior. In other > cases probably you are right and it is over killing. Is that what you > are asking? Well I imagine it is nice to be able to combine a custom framework using wicket ajax as that would probably allow someone to perform the custom AJAX behavior together with rendering wicketcomponents when the behavior is triggered. I am just trying to understand how this works. Right now I understand the simple method of AbstractAjaxBehavior.] I am now just wondering how the approach using wicket ajax works. Is there documentation explaining how to hook in custom client side behavior using wicket ajax. In other words, re-rendering wicket components AND reading a custom payload from the message, and returning a custom payload to be processed by the custom javascript. Both the wicket XML request and response must carry somehow the other information transparently. In the AutocompletBehavior of wiquery they are just getting the response and writing directly to it, ignoring the request target, whereas as I understand it now the request target is the interface towards the response so bypassing it is risky.
