actions execution order

["Rui Alberto L. Gonçalves" <ru...@ptinovacao.pt>]

Hi all,
I've the following situation.

<map:match pattern="remove_attrs_from_session">
<map:select type="request">
 <map:parameter name="parameter-name" value="report-type"/>
 <map:when test="...">
   //REMOVE SOME ATTRIBUTES FROM SESSION
   <map:generate ...
 </map:when>
 
 <map:otherwise>
   <map:generate ...
 </map:otherwise>
 <map:serialize type="xml"/>
</map:match>


<map:match="main">
 <map:aggregate element="root">
   ...
   <map:part src="cocoon:/remove_attrs_from_session"/>
 </map:aggregate>
 <map:transform src="stylesheets/main_common.xsl">
   ...
   //passed some attributes stored in session
 </map:transform>
</map:match>

When pipeline "remove_attrs_from_session" is called from the 
second pipeline ("main"), some attributes are removed from session,
but it seems that they are only removed after the pipeline
"main" completes execution and not in the moment the pipeline
"remove_attrs_from_session" executes the action, because the
removed attributes still available to the stylesheet main_common.xsl.

Aren't actions executed in the first place?
Does cocoon perform a local copy of session to execute the
pipeline?

I hope I made myself clear!! :)

Thanks for any help.

Rui



-- 
Rui Alberto L. Gonçalves <ru...@ptinovacao.pt>
PT Inovação


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org