Hi all,
I encountered a strange bug in an application combining flow and aggegation : each page is an aggregation of navigation+content, and the content is a call to a flowscript.
The bug seems to be related to multiple cocoon: related. I isolated it from the flow :
<map:match pattern="test1.xml"> <map:aggregate element="root"> <map:part src="cocoon:/flow-call.xml"/> <!-- other parts removed --> </map:aggregate> <map:serialize type="xml"/> </map:match>
<map:match pattern="flow-call.xml"> <map:redirect-to uri="cocoon:/flow-view.xml"/> </map:match>
<map:match pattern="flow-view.xml"> <map:generate src="test.xml"/> <map:serialize type="xml"/> </map:match>
Update : the bug occurs also of the <map:aggregate> is replaced by a simple <map:generate src="cocoon:/flow-call.xml"/>
So this seems more related to redirects chaining in internal requests...
Thanks for any hint about this.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
