So the ultimate result of the onClick() method, in this case, is to move to a whole new page, i.e the last line is: setResponsePage(...);, so technically, it probably does not need to be an ajax request, but because of the way we are reusing some code it is.
I commented out the setResponsePage() as a test and the Ajax Console still disappeared. Timo Rantalaiho wrote: > > On Wed, 07 Nov 2007, skatz wrote: >> The Ajax debug console disappears before I can read what it is saying, >> and > > Hmm, I think that normally the ajax debug console should > stay there for javascript executions and ajax requests. > Could it be that the whole page gets loaded somehow? > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Help-understaning-AjaxCallDecorator-problem-tf4760426.html#a13635149 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
