Looks like it wants to use it [1]. You could try running below in the GUI:
Q{java:org.basex.util.Reflect}find("org.apache.xerces.jaxp.validation.XMLSchemaFactory")
/Andy
[1]
https://github.com/BaseXdb/basex/blob/b8c1ae7738664aa3912ade783b8a01a0a2285d25/basex-core/src/main/java/org/basex/query/func/validate/ValidateXsd.java#L65
On 19 July 2016 at 13:10, George Sofianos <gsf.gre...@gmail.com> wrote:
> Thanks, it looks like it's in the classpath. But is it actually used? I
> can't be sure. I have seen some strange things happening with Xerces
> versions in the past with Saxon.
>
> Anyway, it would be great if BaseX can have a feature to change the
> validation options. Should I open a BaseX ticket about it? or is there
> already a way to set these.
>
> https://xerces.apache.org/xerces2-j/features.html
>
>
>
> On 7/19/2016 3:05 PM, Andy Bunce wrote:
>
>> Hi George,
>>
>> Just on point #1
>> I think BaseX does not install Xerces. Entering the line below in the GUI
>> will tell you the version from the JDK
>>
>> Q{java:com.sun.org.apache.xerces.internal.impl.Version}getVersion()
>>
>> For me this returns:
>> Xerces-J 2.7.1
>>
>> If you have manually added Xerces to the classpath, then you can get the
>> version by:
>> Q{java:org.apache.xerces.impl.Version}getVersion()
>>
>> /Andy
>>
>>
>
