[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jos Snellings closed COCOON3-53. -------------------------------- Resolution: Fixed The observed problem was due to using a SimpleCacheKey. It remains a strange fact that this is only observed when the end point is an XMLSerializer. > 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.