[
https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842993#action_12842993
]
Reinhard Poetz commented on COCOON3-53:
---------------------------------------
Both generators (TermGenerator and WorkspaceProvider) create a SimpleCacheKey.
A SimpleCacheKey is always valid and the equals method only checks the passed
object is of type SimpleCacheKey. It is used for components that always create
the same result if the passed events are the same (i.e. there are no external
influences)
You should use some other cache key implementation: Have a look at
ParameterCacheKey or TimestampCacheKey.
> 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.
