[
https://issues.apache.org/jira/browse/WICKET-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-2219.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC3
patch applied. Thanks.
> 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
> Fix For: 1.4-RC3
>
> 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.
