Stefano Mazzocchi wrote: > > <snip> > > -0 for allowing this change before the flowmap semantics are being > worked on. I mean: if you allow something like > > <pipeline> > <act name="pre-matching"/> > <match>...</match> > <match>...</match> > <match>...</match> > </pipeline> > > people start doing > > <pipeline> > <act name="pre-matching"/> > <match>...</match> > <match>...</match> > <match>...</match> > <act name="post-matching"/> > </pipeline> > > and then > > <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? > > 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. 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. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
