You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Chuck Deal (JIRA)" <ji...@apache.org> on 2009/04/08 16:41:13 UTC
[jira] Updated: (WICKET-2219) More detailed error messages in
wicket-ajax.js
[ https://issues.apache.org/jira/browse/WICKET-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Deal updated WICKET-2219:
-------------------------------
Attachment: wicket-ajax.js.patch
This is the patch I made that does what I thought was useful. I'm not tied to it, but I thought this was at least more informative than the current messages.
> More detailed error messages in wicket-ajax.js
> ----------------------------------------------
>
> Key: WICKET-2219
> URL: https://issues.apache.org/jira/browse/WICKET-2219
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.5
> Reporter: Chuck Deal
> Priority: Trivial
> Attachments: wicket-ajax.js.patch
>
>
> I was getting messages in my debug console the simply read
> ERROR: [Object error]
> While at least I knew there was a problem, I had no idea what was causing it or where to look. What was helpful to me was modifying wicket-ajax.js to include a little more information with the error message. At the least, it names the wicket-ajax function that threw the error which jumpstarts the debugging process. For those errors thrown in the catch around an eval() method, I also include the text being eval'ed.
> So, my recommendation is to include this extra text in the error messages to speed debugging of ajax javascript errors
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.