cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Kossakowski (JIRA)" <>
Subject [jira] Closed: (COCOON-2179) Exception generator doesn't work properly
Date Fri, 21 Mar 2008 15:35:31 GMT


Grzegorz Kossakowski closed COCOON-2179.

                     Resolution: Duplicate
    Affects version (Component): Parent values: Cocoon Core(10151). Level 1 values: 2.2.0-RC2(10309).

        Fix version (Component): Parent values: Cocoon Core(10227). Level 1 values: 2.2.0-RC2(10303).

It turns out that commit made by Carsten in r543066 did not incorporate essential change proposed
originally by Alexander Klimetschek. This problem turns out to be the reincarnation of COCOON-2070
that has never been fixed.

> Exception generator doesn't work properly
> -----------------------------------------
>                 Key: COCOON-2179
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Reinhard Poetz
>            Assignee: Grzegorz Kossakowski
>            Priority: Blocker
> I run across some obscure behaviour, when I use the exception generator: The problem
is that it only works every second request.
> When it fails, following exception is thrown:
> Caused by: org.apache.cocoon.ProcessingException: Generator already set. Cannot set genera
> tor 'exception'
>         at <map:generate type="exception"> - file:///F:/os/cocoon/trunk/blocks/cocoon-it/.
> /src/main/resources/COB-INF/sitemap.xmap:211:43
>         at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setGenerator(A
> I don't remember that I have seen this with RC2. 
> I added a sample to cocoon-it and a test case to cocoon-webapp (

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

View raw message