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.

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.

For more conceptual information about selectors see Using and Implementing Matchers and Selectors. For detailed descriptions about all of the available Cocoon selectors, see the user's guide document Selectors in Cocoon. You may also wish to consult the Cocoon API documentation.

What is the difference between a selector and a matcher?

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 Using and Implementing Matchers and Selectors.

Errors and Improvements? If you see any errors or potential improvements in this document please help us: View, Edit or comment on the latest development version (registration required).