You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <de...@velocity.apache.org> on 2009/07/06 18:09:14 UTC
[jira] Resolved: (VELTOOLS-115) Improve exception and HTTP error
management
[ https://issues.apache.org/jira/browse/VELTOOLS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELTOOLS-115.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Thanks, Antonio!
> Improve exception and HTTP error management
> -------------------------------------------
>
> Key: VELTOOLS-115
> URL: https://issues.apache.org/jira/browse/VELTOOLS-115
> Project: Velocity Tools
> Issue Type: Improvement
> Components: VelocityView
> Affects Versions: 2.0
> Environment: Servlet container
> Reporter: Antonio Petrelli
> Fix For: 2.0
>
> Attachments: veltools-exception.diff, veltools-exception.diff
>
>
> Currently the exception management and missing resources are not satisfactory.
> In particular:
> 1. if an exception happen during rendering a template, an exception stack trace is put inside the result, with an HTTP 200 code;
> 2. if a resource is missing, but it is intercepted by the VelocityViewServlet, it renders with a page with HTTP 200.
> It should be:
> 1. HTTP 500 with error page. If it is not possible (if the response is committed), the error page should be included.
> 2. HTTP 404 with error page.
> In both cases the configuration of the webapp should be considered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org