cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Closed] (COCOON3-113) Error invocations get cached
Date Tue, 27 Nov 2012 17:09:59 GMT

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

Francesco Chicchiriccò closed COCOON3-113.
------------------------------------------

    Resolution: Fixed

http://svn.apache.org/viewvc?rev=1414265&view=rev
                
> Error invocations get cached
> ----------------------------
>
>                 Key: COCOON3-113
>                 URL: https://issues.apache.org/jira/browse/COCOON3-113
>             Project: Cocoon 3
>          Issue Type: Bug
>          Components: cocoon-sitemap
>    Affects Versions: 3.0.0-alpha-3
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 3.0.0-beta-1
>
>
> When an error occurs during pipeline execution, an exception is thrown.
> Then, if <map:handle-errors> is configured, a new pipeline execution takes place;
normally, this second execution is successful, showing the stackatrace or a custom error page.
> In this case - i.e. when an error generates a second successful pipeline execution -
this second execution is stored into the cache, associated with the CacheKey originating from
the first execution.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message