[oXygen-user] default validation engine affected by xml-model processing instruction?

George Cristian Bina george at oxygenxml.com
Wed Nov 23 06:50:02 CST 2011

Dear Tara,

I can confirm this is bug and it is present also in 13.1. We will fix 
this for 13.2.
As a workaround please create a validation scenario and the validation 
with Relax NG as an additional validation unit there instead of using 
the xml-model PI. So basically you should have two validation units, one 
with the defaults and another with your specific Relax NG schema.

Best Regards,
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger

On 11/23/11 1:46 PM, Tara Athan wrote:
> I have some XML instances that I would like to validate against both a
> Relax NG schema and an XSD (for testing a re-engineering from XSD to
> Relax NG).
> I want to use the Saxon EE engine for the XSD, as the XSD schema is not
> valid  according to Xerces (which is part of the motivation to switch to
> Relax NG), but gets through Saxon with some warnings.
> I have set the preferences to use Saxon as the default engine, and this
> works fine for batch validation ... until I include the xml-model
> processing instruction for the Relax NG schema in the instances. Then
> the XSD validation reverts to Xerces resulting in failure.
> I am using Oxygen 12.2.
> Is this a known bug?
> Has it been fixed in Oxygen 13 (this might give me the motivation to
> upgrade).
> Thanks, Tara
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user

More information about the oXygen-user mailing list