> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > Stefano Mazzocchi wrote: > >
<snip> > > <pipeline> > > <act name="pre-matching"/> > > <match>...</match> > > <act name="intra-matching"/> > > <match>...</match> > > <match>...</match> > > <act name="post-matching"/> > > </pipeline> > > > > but then the question is: is "intra-matching" performed if the first > > match is successful? 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. > > > > Placing map:act at the same level of map:match can be perceived as a > > design mistake, but might not be since 'matcher' and 'actions' are not > > pipeline components since they don't work on the pipeline directly. > > > > The current semantics of the sitemap stops executing the sitemap, if > a reader of a serializer is found. So any other component following > in the sitemap regardless if it is an action, a matcher or a generator > is ignored. > > So a simple: > <match> > <generate/> > <serialize/> > <act/> > </match> > > reveals the same problem! I think these are two different things: > a) Are only matchers allowed as top level elements? > b) When does the executing of the sitemap stop? Is the example > from above wanted? > > I think we should answer a) with a yes. We saw several examples in > this thread, that a top-level action does make sense. And it would > not break compatibility. Did you meant "No, not only matchers"? > > For b) I'm not sure. It might make sense to execute actions after > the xml pipeline is executed. But changing this is incompatible! > Existing sitemaps would then be executed differently than before. > For example, if you have > <match> > <generate/> > <serialize/> > </match> > <act/> > the action is currently only executed, if the match is not successful. > Changing this would execute the action always! > So I'm -0.5 on this. -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"). Vadim > > Carsten > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
