What is a matcher?
A matcher is a core sitemap component of Cocoon. Matchers are used to determine the flow, order, and components involved in request processing. Matchers typically contain a generator and a serializer. They may redirect requests to other pipelines or call other sitemap resources. Matchers may also be nested with other matchers.
Matchers are executed during pipeline setup. They determine which pipeline will process a URI request. Most typically, the match is based on the requested URI string. However, a number of other matchers exist, for example, Session and Cookie matchers.
In the sitemap file, each matcher has a unique name which is mapped to a java class. One matcher name must be declared as the default matcher. Each matcher may have additional configuration information specified in child elements.
For more conceptual information about matchers see Using and Implementing Matchers and Selectors. For detailed descriptions about all of the available Cocoon matchers, see the user's guide document Matchers 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.
How can I add my FAQ to this document?
Follow the instructions found in How-To Author an FAQ.
How can I suggest improvements to existing FAQs?
Given the rapid pace of change with Cocoon, many individual FAQs quickly become out-of-date and confusing to new users. If you have the relevant knowledge, please consider updating other FAQs on this page for technical errors. If you see a few typos, please consider fixing them too. Follow the instructions found in How-To Author an FAQ.