Create a simple selector to check if the file exists, and if it doesn't call pipeline
A.
David
-Mensaje original-
De: Ali Mesbah [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 19 de junio de 2003 14:10
Para: [EMAIL PROTECTED]
Asunto: pipeline dependencies
Hi,
Is it possible to
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
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
As quoted from Upayavira [EMAIL PROTECTED]:
Another way you can do it is read your original content from disc, then transform it
into something like:
xml
source:write
contentBlah/content
/source:write
contentBlah/content
/xml
This way you repeat your content twice, once to
The thing is I generate a stylesheet in B which is used in A (and in
other pipelines):
match pattern=B
map:generate src=resources/{filename}.xml/
map:transform src=styles/Meta_output.xsl/
map:serialize type=xml/
/map:match
Note that the output of B is a stylesheet (say
As quoted from Upayavira [EMAIL PROTECTED]:
Ali,
Have you seen:
http://wiki.cocoondev.org/Wiki.jsp?page=MetaStylesheets
Maybe that'll help.
It works indeed. I see what I was doing wrong;
In my Meta_output at some places I had something like:
xsl:text disable-output-escaping=yes
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
- Original Message -
From: Nick Entin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 07, 2001 12:02 PM
Subject: Pipeline dependencies
Hello!
Does anybody know is that possible to make one pipeline to be dependent
on another?
Like I have a 2 frames in result - left
It is possible. I'm using that in my site:
map:pipeline
map:match pattern=pd/mergedoc.html
map:generate src=_thesource_/
map:transform src=cocoon:/rtf_merge_data/
map:serialize type=html/
/map:match
/map:pipeline
