Saxon

Hi O'Neil,

thanks for the quick update - is it possible to get a Version with the fix (even just a Release Candidate or Snapshot build) so that we can progress with our project?

Cheers

Jörg Godau

Schütze Consulting AG

Hi Jörg,

Yes I think we can send your a snapshot privately for you to test.

Hi O'Neil,

please send your snapshot to j.godau@schuetze-consulting.ag

Thanks

Jörg...

Hi O'Neil,

the original problem is fixed in the snapshot you sent us, but there is a new problem.

We need to deactivate the secure Processing, as we are dealing with files with over 10000 (tenthousand) elements. We do that with:

@final SchemaFactory schemaFactory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

schemaFactory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, false);@

This causes:

@ org.xml.sax.SAXNotRecognizedException: http://javax.xml.XMLConstants/feature/secure-processing

at javax.xml.validation.SchemaFactory.setFeature(SchemaFactory.java:390)@

Can Saxon deal with such large files? Do we just not need to set the flag? Or is there something we're not understanding?

Cheers

Jörg...

We should probably treat this as a bug, since the Javadoc does say that all implementations are expected to recognize this feature (and by implication, recognize a request to switch it off). But your application should work fine, I think, if you just avoid this call, or ignore the exception if it fails. There's a possibility that the underlying parser might impose size limits on the XML, but we've validated gigabyte-sized files without hitting any limits, so I would be surprised.

Hi Michael,

we'll avoid setting the flag for now, but long term would like to have it active - in case we switch to a differnt implementation, will you open another ticket for this? If so please let us know the ticket number and we can note it in our documentation.

Many thanks for the fast responses!

Cheers

Jörg...

Hi,

I have created the following new bug issue #2414 to keep track of the separate problem reported in comment 5

Marking this bug as resolved. I have created an internal bug issue to keep track of requirement for post build test case. #2432