You may have a look at gaulois-pipe, which is design to cache XSL
compile results, to run multi-files transformation in parallel, and
other simple things made to go fast.
https://github.com/cmarchand/gaulois-pipe/wiki
We use it a lot, as it allows, through a pipeline definition file, to
run various XSL pipelines, without writing anymore java code or shell code.
Best,
Christophe
Le 15/12/2019 à 10:03, Trevor Nicholls trevor(_at_)castingthevoid(_dot_)com a
écrit :
Hi
An application I am working on contains a large number of source
documents which are all run through the same series of
transformations. While initially the build process didn't take long
the cost of repeatedly initialising the XSL processor soon adds up, so
I am looking at ways to streamline it.
Our processor of choice is Saxon (currently we are using 8.7.3) so I
can shift this question to the Saxon list if there are extensions
there that are relevant.
So the question; given a script that essentially includes the following:
cd documents
for d in `cat dlist`; do
cd $d
for f in `cat flist`; do
java -jar $SAXONDIR/saxon8.jar -o $f.new.xml $f.xml
$SCRIPTDIR/transform.xsl doc=$d file=$f
done
done
is there a mechanism which would allow a single Java process to
perform the equivalent?
Thanks
T
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/2837134>
(by email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--