Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <368404082.152401268132007253.JavaMail.jira@brutus.apache.org>
Date: Tue, 9 Mar 2010 10:53:27 +0000 (UTC)
From: "Reinhard Poetz (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
In-Reply-To: <805743823.122821267948347180.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843002#action_12843002 ] 

Reinhard Poetz commented on COCOON3-53:
---------------------------------------

The cache key has to contain everything that influences the output produced by the generator.

I have no idea why HTML serialization makes a difference, but again, the logs should give you some hints.

> Cocoon 3: XMLSerializer caches all
> ----------------------------------
>
>                 Key: COCOON3-53
>                 URL: https://issues.apache.org/jira/browse/COCOON3-53
>             Project: Cocoon 3
>          Issue Type: Bug
>          Components: cocoon-pipeline
>            Reporter: Jos Snellings
>
> After startup, any pipeline/matcher ending in an xml-serializer will
> produce the output of the first request after server startup, regardless of the url, let alone parameters.
> So the first xml pipe that is activated produces the expected output.
> All subsequent calls will echo that output, whatever the url or parameters.
> It takes a server restart to make a pipeline ending in an xml serializer work again.

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