As quoted from Upayavira <[EMAIL PROTECTED]>: > > Is it possible to define pipeline dependencies in the sitemap? > > > > Imagine I have two pipelines A and B. > > Pipeline B has a SourceWritingTransformer and all it does is writing a > > generated document on the filesystem. Pipeline A has its own generator > > and transformer but it depends on the document written by B. So A > > denpends on B. In other words when A is called B has to be called > > first but the output of A sould be serialized to the browser (and not > > the output of B). > > You could try just including pipeline B in with pipeline A using cocoon:, e.g. > > <map:match pattern="B"> > <map:generate...> > <map:transform type="SWT"> > <map:serialize type="xml"/> > </map:match> > > <map:match pattern="A"> > <map:aggregate element="foo"> > <map:part src="cocoon:/B"/> > <map:part src="a-src.xml"/> > </map:aggregate> > <map:transform...> > <map:serialize...> > </map:match> > > If you can get pipeline B to cache, then it will only write if the source of that > pipeline > has changed. > > Then, if necessary, you can ignore the aggregated output from pipeline B, but it is > just > there to enforce the dependency. > > All depends upon the caching of the SourceWritingTransformer. >
Thanks Upayavira. I think with the current implementation that is the only possible way of doing it. Although it's not efficient (you dont actually want to aggregate), it serves the purpose. > Regards, Upayavira > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- -- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
