Okay, well, these are disappointing responses. Especially
since much of the application in this case is written in XSLT
(and is processing and generating a number of collections). I
think I'll take my own counsel on this one. Thanks anyhow.
If you don't have a point in the calling application where it's easy to copy
a file, then your application architecture may be wrong. I think that in
nearly all production applications there should be some kind of framework
that invokes the XSLT (it might be Java, or XProc, or Ant, or Cocoon, or
something else) that allows you at the very least to fiddle around with
input and output files. Ideally it should allow you to construct a pipeline
of transformations. If you don't have such a framework then you'll find
yourself, as the requirements grow, packing more and more logic into a
single stylesheet until it becomes unmaintainable. You're already proposing
to do something in XSLT that would be much more efficiently done elsewhere.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--