Subject: Re: [xsl] Re: XPath that returns nothing From: Michel Hendriksen <michel.hendriksen@xxxxx> Date: Fri, 30 Sep 2011 10:49:04 +0200 |
Using Java to run the transformations could be a better option. I have something like this where sources for good runs are then moved to an archive folder, failed ones goto an 'bad case' folder etc. Also reports are output for these cases. After fixing, they can then be put back in the source folder. The XSL engine would do one file at a time and can go to the next on a critical error. You can even catch the errors yourself and handle them the way you want. You could even send out email if you so desire. Michel On Thu, Sep 29, 2011 at 11:01 PM, Olivier Lefevre <lefevrol@xxxxxxxxx> wrote: > On 9/27/2011 10:42 AM, Andrew Welch wrote: >> >> Out of interest, why do you ask? > > 1) curiosity > 2) for eventual use as a "null" object or case (I'm using Java) > > -- O.L.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Re: XPath that returns nothin, Olivier Lefevre | Thread | [xsl] XML pretty printer, John Christopher |
Re: [xsl] an error I do not underst, Michael Kay | Date | [xsl] () eq () vs () = (), Andrew Welch |
Month |