You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Ertl (JIRA)" <ji...@apache.org> on 2010/08/17 20:39:17 UTC
[jira] Created: (WICKET-2997) AbstractResource should give access
to the error message for http errors
AbstractResource should give access to the error message for http errors
------------------------------------------------------------------------
Key: WICKET-2997
URL: https://issues.apache.org/jira/browse/WICKET-2997
Project: Wicket
Issue Type: Improvement
Reporter: Peter Ertl
Attachments: set-error-message.patch
AbstractResource lets you set the errorCode if something goes wrong but not a custom error message. This is really annoying because the user/developer does not get any hint why something goes wrong.
current:
response.sendError(data.getErrorCode(), null); // <------ always null, no custom error message
I attached a simple patch to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2997) AbstractResource should give access
to the error message for http errors
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900040#action_12900040 ]
Hudson commented on WICKET-2997:
--------------------------------
Integrated in Apache Wicket 1.5.x #247 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/247/])
> AbstractResource should give access to the error message for http errors
> ------------------------------------------------------------------------
>
> Key: WICKET-2997
> URL: https://issues.apache.org/jira/browse/WICKET-2997
> Project: Wicket
> Issue Type: Improvement
> Reporter: Peter Ertl
> Assignee: Igor Vaynberg
> Attachments: set-error-message.patch
>
>
> AbstractResource lets you set the errorCode if something goes wrong but not a custom error message. This is really annoying because the user/developer does not get any hint why something goes wrong.
> current:
> response.sendError(data.getErrorCode(), null); // <------ always null, no custom error message
> I attached a simple patch to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2997) AbstractResource should give access
to the error message for http errors
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2997.
-----------------------------------
Assignee: Igor Vaynberg
Resolution: Fixed
> AbstractResource should give access to the error message for http errors
> ------------------------------------------------------------------------
>
> Key: WICKET-2997
> URL: https://issues.apache.org/jira/browse/WICKET-2997
> Project: Wicket
> Issue Type: Improvement
> Reporter: Peter Ertl
> Assignee: Igor Vaynberg
> Attachments: set-error-message.patch
>
>
> AbstractResource lets you set the errorCode if something goes wrong but not a custom error message. This is really annoying because the user/developer does not get any hint why something goes wrong.
> current:
> response.sendError(data.getErrorCode(), null); // <------ always null, no custom error message
> I attached a simple patch to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2997) AbstractResource should give access
to the error message for http errors
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-2997:
-------------------------------
Attachment: set-error-message.patch
> AbstractResource should give access to the error message for http errors
> ------------------------------------------------------------------------
>
> Key: WICKET-2997
> URL: https://issues.apache.org/jira/browse/WICKET-2997
> Project: Wicket
> Issue Type: Improvement
> Reporter: Peter Ertl
> Attachments: set-error-message.patch
>
>
> AbstractResource lets you set the errorCode if something goes wrong but not a custom error message. This is really annoying because the user/developer does not get any hint why something goes wrong.
> current:
> response.sendError(data.getErrorCode(), null); // <------ always null, no custom error message
> I attached a simple patch to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.