David Bertoni wrote:
John Snelson wrote:
It seems to me that the SGXMLScanner is at fault here, since XQilla
works fine with the IGXMLScanner.
The problem seems to be caused because the IGXMLScanner uses a method
called processSchemaLocation() to parse the schema location string,
where as the SGXMLScanner uses XMLString::tokenizeString().
This points out the maintenance nightmare of the various scanners.
I'd bet the vast majority of users never use DGXMLScanner or
SGXMLScanner, and I've never seen a single test that proves their
performance is any better than that of IGXMLScanner. Perhaps we
should consider deprecating them so we can avoid the overhead?
I have been toying with the idea of making the validator work as an
advanced handler, so that the 4 scanners become 1 scanner + schema
validator + dtd validator plugged on demand. Does anybody have an idea
if the validator code can be (easily) moved out of the scanner?
Alberto
