Project

Profile

Help

Forums » Help »

on directory transforms, an error stops all

Added by Anonymous almost 16 years ago

Legacy ID: #5162525 Legacy Poster: Curieux (curieuxfr)

When I run transform.exe (dot.net version) to transform a complete directory, if one of the files causes an error, the remaining files won't be transformed. In other words, an error stops the batch process, not only the current file processing. The -warnings option does not change anything. Of course, I can create a batch process with 'for' command, but it is extremely slow (about 3 seconds a file). Is there any mean to ignore errors in transform.exe ? Thank you


Replies (3)

Please register to reply

RE: on directory transforms, an error stops a - Added by Anonymous almost 16 years ago

Legacy ID: #5163899 Legacy Poster: Michael Kay (mhkay)

I will consider this as a future requirement. However, I think that if you want detailed control over the behaviour of transformations like this then it is time to use the Java (or .NET) API rather than doing everything from the command line. Michael Kay Saxonica

RE: on directory transforms, an error stops all - Added by Anonymous almost 16 years ago

Legacy ID: #5163982 Legacy Poster: David Lee (daldei)

This is exactly the sort of use case that xmlsh was designed for (www.xmlsh.org). xmlsh uses saxon and allows you to write scripts that all run within the same JVM so it doesnt incur the startup penalty of having to launch a sub-process for each file, but gives you the kind of scripting control that is beyond the scope of batch processing within a single transformation invocation, but without having to write directly to the API's. Disclaimer: xmlsh is in "pre alpha" stage. I wouldnt recommend it for production use (yet) but it may work well for what your trying to do. -David Lee www.xmlsh.org

RE: on directory transforms, an error stops a - Added by Anonymous almost 16 years ago

Legacy ID: #5198310 Legacy Poster: Michael Kay (mhkay)

I haven't been able to reproduce this behaviour. The code is designed to carry on processing subsequent files if one transformation fails, and in my tests, it does so. Perhaps there are some kinds of failure that it doesn't catch correctly? Please could you supply more specific evidence. Sorry about the delay in investigating this, I have been on vacation. Michael Kay Saxonica

    (1-3/3)

    Please register to reply