why would it be onsuccess path? this is something that runs clientside... they are executed every time the component rendered, and no you shouldnt touch ajaxreqesttarget from a call decorator, notice how it is not passed in...
-igor On Thu, Mar 20, 2008 at 2:38 PM, Matthew Young <[EMAIL PROTECTED]> wrote: > >add an iajaxcalldecorator override failed script > > Would that work if failure happen late in rendering? By that time, Wicket > would be on the onSuccess path, right? > > For my Wicket education: I notice the IAjaxCallDecorator callbacks are only > called once. So are these for fixed static script only? And that I should > use target.appendJavascript() for dynamic JS? > > > On Thu, Mar 20, 2008 at 1:21 PM, Igor Vaynberg <[EMAIL PROTECTED]> > wrote: > > > > > On Thu, Mar 20, 2008 at 12:59 PM, Matthew Young <[EMAIL PROTECTED]> wrote: > > > Small wish: in GMail, when their Ajax submit fails (either user submit > > or > > > auto background submit), they don't go to a new page, they flash a > > message > > > "System error, trying again." It would be great if Wicket can support > > this > > > way of Ajax error handling when error happen very late during render. > > > > this we do support. just throw an error, and in your button add an > > iajaxcalldecorator, override failed script and make it show the popup > > > > -igor > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
