CODEWITHSUNDEEP
xmlupgradesaxonserving
Yuri
Yuri

Reputation: 4478

Upgrading Saxon in ServingXML results in "XML Parser does not recognize the feature http://xml.org/sax/features/validation"

I use ServingXML (1.1.2) for various plain-XML transformations. I need to upgrade the Saxon lib used by ServingXML to up to date Saxon 9.6 line (currently Saxon-HE 9.6.0.6J).

Reason for this is: I'm forced to use the recent Saxon line and I use both Saxon and ServingXML with a preloading app container which - sadly - restricts using multiple lib versions simultaneously.

Anyway, I've replaced the Saxon libs and made minor changes to the ServingXML code to match Saxon API differences.

It seems to work fine. However, a single ServingXML run the upgraded Saxon spits tens of lines:

 XML Parser does not recognize the feature http://xml.org/sax/features/validation

It seems odd to me because I'm unable to find any place in the ServingXML source where would that wrong feature setting to Saxon happen.

Upvotes: 0

Views: 466

Answers (2)

Michael Kay
Michael Kay

Reputation: 163488

I took a look in the source code of ServingXML. It includes an implementation of XMLReader (package com.servingxml.util.xml.AbstractXMLReader) which fails to recognize the feature http://xml.org/sax/features/validation

I suspect this is the parser you are using. But I don't know how to help with your problem. Is the author of ServingXML responding to requests for help?

Upvotes: 0

Michael Kay
Michael Kay

Reputation: 163488

A bit of information that might help you in your investigation.

Firstly, it's a warning. After outputting the warning, Saxon continues as normal. In effect, the request to set this feature on the parser is ignored.

Secondly, the message occurs after Saxon calls parser.setFeature() with the specified feature name, and the parser throws a SAXNotRecognizedException. It can occur whether the feature is being set on or off.

Thirdly, Saxon attempts to set this feature if DTD validation is requested, for example by calling Configuration.setValidation(). However, there are many other paths that could cause this request.

So there are two things happening here. (A) the application is (by some means) requesting DTD validation of source documents, and (B) the application has somehow configured an XML parser that does not support DTD validation (or that does not recognise the request).

Upvotes: 1

Related Questions