Hi Michael,

Good to hear that our problem could be reproduced locally. Did you make any progress looking into this issue?


On Mon, Feb 6, 2012 at 7:44 PM, Michael Kay <mike@saxonica.com> wrote:
On 06/02/2012 17:32, Daan Stroep wrote:
> Hi,
> We're using Saxonee- to perform schema-aware xslt
> transformations and are very pleased with the results so far. In some
> cases however, our xslt fails to produce a result document that
> validates against the supplied schema, causing saxon to terminate the
> transformation and not produce output. Since having access to the
> invalid output would make manual correction/debugging a lot easier, I
> would like to be able to instruct saxon to treat validation errors as
> non-fatal.
> In the javadoc I found a couple of methods
> (setConfigurationProperty(FeatureKeys.VALIDATION_WARNINGS,
> Boolean.TRUE); and setValidationWarnings(true); on
> net.sf.saxon.Configuration) that look useful. Unfortunately
> configuring saxon (either directly or via FeatureKeys) does not seem
> to have the desired effect. Validation errors still cause the
> transformation to be halted without producing output. Could it be that
> we're overlooking a setting somewhere?  I've included some sample code
> with this mail.
I've done a quick test and I have a feeling this isn't working properly.
It's recovering from some validation errors but not all. I'll take a
look at it and see what I can do.

Michael Kay

Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
saxon-help mailing list archived at http://saxon.markmail.org/