You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2012/11/27 18:05:58 UTC
[jira] [Created] (COCOON3-113) Error invocations get cached
Francesco Chicchiriccò created COCOON3-113:
----------------------------------------------
Summary: 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ò
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
[jira] [Commented] (COCOON3-113) Error invocations get cached
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON3-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504912#comment-13504912 ]
Hudson commented on COCOON3-113:
--------------------------------
Integrated in Cocoon-trunk #222 (See [https://builds.apache.org/job/Cocoon-trunk/222/])
[COCOON3-113] Explicitly set type to 'noncaching' when executing error pipelines (Revision 1414265)
Result = ABORTED
ilgrosso : http://svn.apache.org/viewvc/?view=rev&rev=1414265
Files :
* /cocoon/cocoon3/trunk/cocoon-sitemap/src/main/java/org/apache/cocoon/sitemap/node/PipelineNode.java
> 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
[jira] [Assigned] (COCOON3-113) Error invocations get cached
Posted by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON3-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò reassigned COCOON3-113:
----------------------------------------------
Assignee: Francesco Chicchiriccò
> 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
[jira] [Closed] (COCOON3-113) Error invocations get cached
Posted by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org>.
[ 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