Hi,
 
I have a scenario where I am aggregating content from three sources, one of which is an XSP retrieved using internal cocoon protocol. This XSP calls request.setParameter() to indicate a status.
 
The aggregation event is followed by an action that tests this status, but it always is set to null.
 
Question: am I correct in assuming that the same request instance is used across all internal cocoon protocol requests?
Question: if this is the case, is there a reason which my attribute should be lost?
 
Many thanks,
Adrian
 
=== begin:sitemap fragment ===
    <map:match pattern="*.form">
      <map:generate type="serverpages" src=""/>
      <map:serialize type="xml"/>
    </map:match>
 
    <map:match pattern="*.update">
      <map:generate type="serverpages" src=""/>
      <map:serialize type="xml"/>
    </map:match>
   <map:match pattern="update_*.html">
       <map:aggregate element="page">
        <map:part src=""/>
        <map:part src=""/>
        <map:part src=""/> <!-- this sets the request attribute -->
      </map:aggregate>
      <map:act type="check-commit-succeed"/> <!-- this tests the request attribute, and re-directs if success -->
      <map:transform src=""/>
      <map:serialize/>
   </map:match>
 
=== end: sitemap fragment ===

Reply via email to