Wicket's default Ajax handling is for "repainting" of components.
As I have written, take a look at AutoCompleteBehavior#onRequest() Sven On 04/03/2013 09:52 PM, heikki wrote:
Eventually I'd probably do something with it other than only displaying it :-) So maybe my approach is not ideal ? In short, and more generally put, I want to be able to construct a URL client-side dynamically to do an Ajax request using Wicket.Ajax.get(), and then do something with the response. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AbstractDefaultAjaxBehavior-response-handling-tp4657714p4657723.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org