Solved. Currently I do it like the following: new Wicket.Ajax.Call ().loadedCallback (response). But it looks like a bit of hack. I would request to decouple the javascript method loadedCallback of the class Wicket.Ajax.Call that actually process a wicket ajax envelope. The use cases may be different. For instance one can use an alternative ajax facility like that jQuery or Prototype offer to have a fine-grained control under request headers. Or like in my case to be able to post data (for uploading files) using an iframe and then to update a page in a regular manner avoiding a second client-server round-trip which will involve a regular wicket ajax call. Should I create an issue for that?
On Sat, Mar 14, 2009 at 7:34 PM, Vitaly Tsaplin <[email protected]> wrote: > Hi guys, > > Is there any way to process a wicket ajax envelope sent in some > non-wicket way like using jQuery or Prototype? > It seem that I can somehow utilize loadedCallback () but i don't > know how to call it right way. > > Vitaly > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
