[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842957#action_12842957 ]
Jos Snellings commented on COCOON3-53: -------------------------------------- - No, I cannot say your test is wrong. The test clearly shows that the right response is returned from the cache - It must be somehow 'subtle' - Yesterday I looked into CachingPipeline and I found everything sound - Yet my test case on a browser stands. If you want I can describe it in detail ==> the next candidate to look at is simplecache. It is hard to imagine what can go wrong here, as it is based upon a map. The only thing I can imagine: - could it be that there is a situation where different cache keys map onto the same content? - my pipes have no jmxname. Can that be a problem? I think not. ==> the thing to do is probably: I try put a finger on the problem at my side and deliver a very specific test case, for I believe the problem is quite specific. I will keep this group posted. > 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.