Robert Mouat wrote:
> The above example feels a little contrived -- are there any real use-cases
> when this might be needed? And will it always be obvious to the component
> that it will need a selector?
thought of one... a cocoon pipeline:
<map:pipeline>
<map:match pattern="*.html" type="wildcard">
<!-- ... -->
</map:match>
<map:match pattern="*.css" type="wildcard">
<!-- ... -->
</map:match>
</map:pipeline>
a pipeline selector could be created that took a URL and determined the
appropiate pipeline from that -- for each '<map:match/>' it could look up
the matcher and use that to compare the URL provided with the pattern.
[I think that I may have abused the term 'pipeline' above]
Robert.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
