You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/04/07 17:24:34 UTC

[jira] Resolved: (SLING-565) Prevent multiple wrapping of exceptions thrown in included requests

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

Carsten Ziegeler resolved SLING-565.
------------------------------------

       Resolution: Fixed
    Fix Version/s: Engine 2.1.0
                   Scripting Core 2.0.12
         Assignee: Carsten Ziegeler

I'm setting this to resolved as I've changed/improved the wrapping lately. If we see unnecessary wrapping again, we should open a new specific bug about the exact problem :)

> Prevent multiple wrapping of exceptions thrown in included requests
> -------------------------------------------------------------------
>
>                 Key: SLING-565
>                 URL: https://issues.apache.org/jira/browse/SLING-565
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine, Scripting
>    Affects Versions: Scripting Core 2.0.2, Engine 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting Core 2.0.12, Engine 2.1.0
>
>
> Currently if an exception occurrs while processing a script in an included request, the exception is wrapped. If the exception happens in a script included over multiple levels, the exception is wrapped multiple times.
> Rather than re-wrapping these exceptions multiple times, wrappings should be replaced when forwarding wrapped exceptions.
> One such exception wrapping takes place when recursively including the same resource such that a InfiniteIncludeLoopException is thrown.

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