Below sitemap snippet just seems so counter-intuitive that i thought i'ld share it.
<map:match pattern="*.*">
<map:act type="resource-exists">
<map:parameter name="url" value="file://{1}.{2}"/> <map:aggregate element="aggregation" label="debug1">
<map:part src="file://{../1}.{../2}"/>
<map:part src="cocoon:/{../1}"/>
</map:aggregate>
......
The url action parameter does not need the extra {../} while the ones inside the aggregation do! (note that aggregation can be replaced by plain transformers etc)
I guess the reason is that the src parameter belongs to the action level itself.
Exactly.
Admit, this looks strange (and had me going for a few minutes!)
Therefore you can now use flow instead :) We know the counter-intuitiveness, but any change on this (they were discussed) would break backwards compatibility).
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
