Cannot parse XML Document

I am evaluating Oracle XDK for xml parsing and such.  I used to use Saxon version 8, which used to work just fine, so I know this is not an issue with my liquibase scripts, it has to do with the Oracle XDK.

I tried to load a liquibase script, and I got the following error.  Note, I cannot access the XSD from the browser either…

liquibase.exception.ChangeLogParseException: Error parsing line 5 column 84 of C:/development/workspaces/subversion/jira/OIPA-749/INSURANCE.PAS/pas.test/src/test/database/client/VAPolicyClients.changelog.xml: <Line 5, Column 84>: XML-24500: (Error) Can not build schema ‘<a href=‘’’ target=’_blank’>’ located at ‘<a href=‘’’ target=’_blank’>’
at liquibase.parser.core.xml.XMLChangeLogSAXParser.parse(
at liquibase.Liquibase.update(

Caused by: oracle.xml.parser.schema.XSDException: invalid facet “pattern” for type “simpleType”
at oracle.xml.parser.v2.XMLError.flushErrorHandler(
at oracle.xml.parser.v2.XMLError.flushErrors1(
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(
at oracle.xml.parser.v2.XMLParser.parse(
at liquibase.parser.core.xml.XMLChangeLogSAXParser.parse(
… 37 more
Caused by: oracle.xml.parser.schema.XSDException: invalid facet “pattern” for type “simpleType”
at oracle.xml.parser.schema.XSDBuilder.buildSchema(
at oracle.xml.parser.schema.XSDValidator.processSchemaLocation(
at oracle.xml.parser.schema.XSDValidator.startElement(
at oracle.xml.parser.v2.NonValidatingParser.parseElement(
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(

Thanks Nathan, as always you are SUPER helpful.

I am seeing the parsing issue with Oracle XDK, not Saxon.  Saxon works quite well.

I think it is also due to the XSD being pulled from the internet.  Any idea on how to get it to stop?  Is there a property, or maybe a change in the code that would tell it not to pull the XSD from the internet?

Ahh, even though it looks like the schema is now available from the URL, I am getting the same exception that I posted earlier.

There is logic to keep liquibase from pulling the schema from the internet, but it may not work with saxon.  I’ll have to see why the server is throwing an error, that could be what is causing your problem. 


It looks like a problem with what the saxon parser supports for xsd syntax.  Line 5 of the xsd uses a  <xsd:pattern value="${[\w.]+}"/> declaration to make sure that properties follow the correct syntax. 

Is there a newer parser that may support that?