You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2008/04/20 05:20:05 UTC

[jira] Resolved: (WW-2594) XSL errors in action of type="xslt" generate uncatchable exceptions

     [ https://issues.apache.org/struts/browse/WW-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown resolved WW-2594.
---------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.2
         Assignee: Don Brown

Changed it to throw exceptions on error and fatal exceptions, but just log warnings.

> XSL errors in action of type="xslt" generate uncatchable exceptions
> -------------------------------------------------------------------
>
>                 Key: WW-2594
>                 URL: https://issues.apache.org/struts/browse/WW-2594
>             Project: Struts 2
>          Issue Type: Bug
>         Environment: Windows XP, WebSphere 6.1.7
>            Reporter: Victor Voronenko
>            Assignee: Don Brown
>             Fix For: 2.1.2
>
>
> When XSL file attached to the action of result type="xslt" has even simple error (e.g. missing single quote), then the exception it generates can not caught by any means. JSP defined to handle the result type="error" for this action is ignored and exception is promoted to front-end as HTTP 404 (page not found) error.
> The situation is not limited by only syntax errors in XSL. The problem is even more generic. Eventually any error during XSLT would break the action and this exception may not be caught.
> The problem is that XSLT is performed out of Action class and Struts does not offer any way to register an exception handling for this operation. It might be possible to instantiate the XSLTResult class but it is not clear (not documented) if there is a way to set it as default transformation class.
> Struts should give users means of control over XSLTResult. The best way would be if action classes could implement some XSLT interface with the control over exception handling, URL resolving etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.