Configure XML#builder() to use setValidating or setSchema or none #116
Comments
|
since there's only two usage for DocumentBuilderFactory.newInstance() we could :
Any preference for a pull request ? (later one is only supported since 1.6) |
|
Since there are several places where I have to created XML related classes, the more general solution of a SPI would be desirable. package io.jenetics.jpx;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.stream.XMLInputFactory;
import javax.xml.stream.XMLOutputFactory;
public abstract class XMLProvider {
protected XMLProvider() {
}
// Used for reading files.
public XMLInputFactory xmlInputFactory() {
return XMLInputFactory.newInstance();
}
// Used for writing files.
public XMLOutputFactory xmlOutputFactory() {
return XMLOutputFactory.newInstance();
}
// Used for creating GPX extensions documents.
public DocumentBuilderFactory documentBuilderFactory() {
final DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setValidating(true);
factory.setIgnoringElementContentWhitespace(true);
factory.setNamespaceAware(true);
return factory;
}
public static XMLProvider provider() {
// Do service lookup and return default impl if nothing is found.
return null;
}
}I think this could solve the XML problems once and for all ;-) |
|
Merged into r1.7.0 branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For now it calls
factory.setValidating(true);which is inappropriate in some use case :Would be great to be able to configure the behaviour for
factory.newDocumentBuilder()The text was updated successfully, but these errors were encountered: