You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by da...@cocoon.zones.apache.org on 2005/09/22 15:56:05 UTC
[DAISY] Created: Action FAQs
A new document has been created.
http://cocoon.zones.apache.org/daisy/legacydocs/715.html
Document ID: 715
Branch: main
Language: default
Name: Action FAQs
Document Type: Document
Created: 9/22/05 1:55:51 PM
Creator (owner): Helma van der Linden
State: publish
Parts
=====
Content
-------
Mime type: text/xml
Size: 1304 bytes
Content:
<html>
<body>
<h2>What is an Action?</h2>
<p>An Action is a sitemap component that manipulates runtime parameters based on
request and application state. An Action's result is available in the sitemap as
map of name/value pairs. Detailed information on actions may be found in
<a href="daisy:579">Creating and Using Actions</a>.</p>
<h2>Why does Cocoon return an error when I add an action to a pipeline?</h2>
<p>The pipeline was working fine before the action was added. After the change,
Cocoon seems unable to find the file specified in the variable that is returned
by the matcher.</p>
<pre><map:match pattern="*">
<map:act type="validate-session">
<map:generate type="serverpages" src="{../1}.xsp"/>
</map:act>
<map:serialize/>
</map:match>
</pre>
<p>Please note in the above example the "<em><tt>../1</tt></em>".</p>
<p>Map objects returned from matchers and actions are organised
<em>hierarchically</em>. Therefore, old map objects are not replaced by new
ones, such as the map objects returned by the validate-session action above.
Because older map objects are still accessible through a path expression, new
ones are accessed differently. Here "<tt>../1</tt>" references key ( or
"variable") "1" in the next to last Map.</p>
</body>
</html>
Collections
===========
The document belongs to the following collections: legacydocs