[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all

[Jos Snellings (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842613#action_12842613
 ] 

Jos Snellings commented on COCOON3-53:
--

This is only true for CachingPipeline!
AsyncCachingPipeline is not affected.

 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.

[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all

[Reinhard Poetz (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842756#action_12842756
 ] 

Reinhard Poetz commented on COCOON3-53:
---

I can't reproduce your problem: see #testCachingOfDifferentPipelines() 
http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample-webapp/src/test/java/org/apache/cocoon/it/CachingOfPipelinesTest.java

The pipeline can be found at 
http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/sitemap.xmap,
 lines 50 - 56.

Is my test wrong?

 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.