AElfred (or at least, the version built into Saxon) is a non-validating parser. If you want to validate the source document, you can use Saxon with a different SAX parser such as Xerces or Crimson.
Mike Kay
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It may not be validating, but Saxon transform still fails if it cannot resolve the URI to the dtd. How about a flag to continue if the URI cannot be resolved?
I am trying to integrate Mike Walsh's URI Resolver class (http://www.sun.com/xml/developers/resolver). It runs okay by itself, but I cannot get Saxon to find it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not really in the XML parser business: I include AElfred in the Saxon distribution as a convenience to users, and I don't want to start making enhancements to it. If you can find an XML parser that does what you want, use that one instead.
Mike Kay
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm looking for any flag or option to disable or enable xml source file validation with aelfred parser, using saxon xslt processor.
JL
AElfred (or at least, the version built into Saxon) is a non-validating parser. If you want to validate the source document, you can use Saxon with a different SAX parser such as Xerces or Crimson.
Mike Kay
It may not be validating, but Saxon transform still fails if it cannot resolve the URI to the dtd. How about a flag to continue if the URI cannot be resolved?
I am trying to integrate Mike Walsh's URI Resolver class (http://www.sun.com/xml/developers/resolver). It runs okay by itself, but I cannot get Saxon to find it.
I'm not really in the XML parser business: I include AElfred in the Saxon distribution as a convenience to users, and I don't want to start making enhancements to it. If you can find an XML parser that does what you want, use that one instead.
Mike Kay