Vadim Gritsenko wrote:
> But you can rephrase this:
>
> <pipeline>
> <match pattern="**"><act name="pre-matching"/></match>
> <match>...</match>
> <match pattern="**"><act name="intra-matching"/></match>
> <match>...</match>
> <match>...</match>
> <match pattern="**"><act name="post-matching"/></match>
> </pipeline>
>
> This is perfectly legal now and leaves possibility for the same
> questions.
> So it does not make sense to disable this functionality (unmatched
> actions)
> because of such argument.
ok
<snip/>
> -10 on changing current sitemap semantics. It's even worse then breaking
> compatibility. For before pipeline execution / after pipeline execution
> actions, it is better to have another kind of component, which is
> similar to actions, but with different semantics and name (e.g.,
> "pipeline-action"; current actions could be thought as
> "sitemap-action").
-100000 on breaking back compatibility for this.
-1 on having two different semantics for a component that has the very
same behavior but just happens to live in different places.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
