You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2007/09/01 04:01:34 UTC

[jira] Resolved: (STR-2755) InsertTag makes it hard to see JSP errors.

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

Paul Benedict resolved STR-2755.
--------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.4.0
         Assignee: Paul Benedict  (was: Struts Developers)

This issue has been fixed by STR-2896. Root exceptions are now uniformly nested.

> InsertTag makes it hard to see JSP errors.
> ------------------------------------------
>
>                 Key: STR-2755
>                 URL: https://issues.apache.org/struts/browse/STR-2755
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Tiles 1 Plugin
>    Affects Versions: 1.3.0
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Geoff Bennett
>            Assignee: Paul Benedict
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: Current Implementation.txt, Patch.txt, Patch.txt, Patch.txt, Proposed Implementation.txt
>
>
> At the moment when there is a JSP error the logged error message doesn't give 
> any usefull information. The message just tells us what JSP had the error in 
> it and the message from that original error. The logged stacktrace is also not 
> helpful and just points to InsertTag.doInclude().
> Apart from the logged message, the exception that is thrown results in the 
> culprit on the offending JSP being found after the third backtrace with 
> everything before it being pretty much useless information.
> The root exception should be logged and only the root exception thrown.

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