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 16:07:29 UTC

[DAISY] Created: Cocoon Sitemap Selector FAQs

A new document has been created.

http://cocoon.zones.apache.org/daisy/legacydocs/718.html

Document ID: 718
Branch: main
Language: default
Name: Cocoon Sitemap Selector FAQs
Document Type: Document
Created: 9/22/05 2:07:14 PM
Creator (owner): Helma van der Linden
State: publish

Parts
=====

Content
-------
Mime type: text/xml
Size: 1490 bytes
Content:
<html>
<body>

<h2>What is a selector?</h2>

<p>A selector is a core sitemap component of Cocoon. Selectors are designed to
evaluate a generally simple boolean expression regarding some part of the
environment (request URI, headers, or cookies, for example). The result of this
evaluation determines which pipeline fragments should be combined within a given
pipeline. Selectors are executed during pipeline setup.</p>

<p>In the sitemap file, each selector has a unique name which is mapped to a
java class. One selector name must be declared as the default selector. Each
selector may have additional configuration information specified in child
elements.</p>

<p>For more conceptual information about selectors see
<a href="daisy:575">Using and Implementing Matchers and Selectors</a>. For
detailed descriptions about all of the available Cocoon selectors, see the
user's guide document <a href="daisy:436">Selectors in Cocoon</a>. You may also
wish to consult the Cocoon API documentation.</p>

<h2>What is the difference between a selector and a matcher?</h2>

<p>Both matchers and selectors can be used to determine the flow, order, and
components involved in request processing. Their differences include the
complexity of the decisions they can make about processing as well as the values
they return to the sitemap. For a more detailed discussion of their similarities
and differences, see <a href="daisy:575">Using and Implementing Matchers and
Selectors</a>.</p>

</body>
</html>

Collections
===========
The document belongs to the following collections: legacydocs