cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upayavira" ...@upaya.co.uk>
Subject Re: pipeline dependencies
Date Fri, 20 Jun 2003 08:51:05 GMT
> > 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.

Another way you can do it is read your original content from disc, then transform it 
into something like:

<xml>
  <source:write>
    <content>Blah</content>
  </source:write>
  <content>Blah</content>
</xml>

This way you repeat your content twice, once to go into the SWT, and once to go on 
to the output. Your following transformer then just strips out any nodes in the SWT 
namespace.

Make sense?

Can you explain a little more _why_ you want to be writing to disk? That'll help me 
understand how best you can achieve your requirements.

Regards, Upayavira


<map:match ...>
  <map:generate src="original source">
  <map:transform src="make_

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org


Mime
View raw message