[
https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842997#action_12842997
]
Jos Snellings commented on COCOON3-53:
--------------------------------------
Yes, I thought about that, SimpleCacheKey is all too Simple. I kept it mainly
because it was in the samples:
it is not expected that a generator produces the same result.
but why do pipelines with the same Starters (Termgenerator or
WorkspaceProvider) are perfectly OK with the cache when they end in html
serialization?
Anyway, I will use a parameter cache and verify the cache behaviour is correct.
If it does, I close this issue.
> 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.
