Hi everyone,
I am still a bit unsure regarding the run priority of "oxf:null-serializer".
My intention is that I would like to have the oxf:url-generator finished its job - the loading pdf to the memory is completely finished before the deletion processor is started to delete the physical pdf file in the file system.
...
<p:processor name="oxf:xslt">
<p:input name="data" href="#publication-start-request"/>
<p:input name="config">
<config xsl:version="2.0" xmlns:xsl="
http://www.w3.org/1999/XSL/Transform"> <url>
<xsl:value-of select="concat('file:///',(//path-to-outputpdf)"/>
</url>
<mode>binary</mode>
</config>
</p:input>
<p:output name="data" id="PDF_Url"/>
</p:processor>
<p:processor name="oxf:url-generator">
<p:input name="config" href="#PDF_Url"/>
<p:output name="data" id="PDF"/>
</p:processor>
<p:processor name="oxf:null-serializer">
<p:input name="data" href="#PDF"/>
</p:processor>
<p:processor name="fs-delete-processor">
<p:input name="data" href="#path-to-outputpdf-config"/>
<p:output name="data" id="output-path-to-outputpdf"/>
</p:processor>
<p:processor name="oxf:null-serializer">
<p:input name="data" href="#path-to-outputpdf"/>
</p:processor>
....
So the above sample code and in order of the oxf:null-serializer in the context work for my purpose or I am missing some points ?
Thanks,
Huong
Locked
