you mentioned FireBug How about setting a breaktpoint in 'wicket-ajax-debug.js' ? Or if recompiling the framework is an option, the logging could be modified in that file. wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax-debug.js
mf 2010/3/30 MattyDE <[email protected]> > > Yeah i know this window. But there are all INFO outputs too and you could > oversee an error very easy... > > And for instance if i evaluate some "overlay functionality" on my page, i > cant open the debug window, cause any mouseclicks are catched by a > overlaying layer ... > > > Martin Funk-3 wrote: > > > > Could you elaborate on your problem a little more? > > What precisely do you want to do? > > > > If the Application is started in develompment mode the > 'WICKET_AJAX_DEBUG" > > window should be available on any Page containing Wicket-Ajax components. > > (The link in the right bottom corner) > > > > mf > > > > 2010/3/30 Martin U <[email protected]> > > > >> Hi Folks, > >> > >> > >> have everyone of you any experience in catching the wicket-ajax and > >> js-errors with the Firebug? > >> > >> Easily we just need to overwrite WicketAjaxDebug.logError... but how? > >> > >> > >> Thanks for any advice! > >> > > > > > > -- > View this message in context: > http://old.nabble.com/Catch-Wicket.Error-with-FireBug-tp28080433p28082310.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
