Documentbuilderfactory validating black shemale dating
I recommend always parsing with namespaces enabled, with one exception: in legacy code that uses XPath or XSLT.
As I describe elsewhere, XPath has its own hoops with regard to namespaces.
Practical XML: Parsing So you've built some XML, now what do you do? After all, it doesn't do you much good as a bunch of bytes on a disk.
In my experience, a DOM document is the most usable form for parsed XML, because it can be accessed multiple times once parsed.
But for everything else (including new code using XPath), namespace-aware parsing should be your default.
I'm not really sure I want to cut a new 1.x release at all anymore.
The topic hasn't really come up before, I guess most people aren't using DTDs at all or use DTDs with only local SYSTEM ids (or none at all).
I get your point about reproducibility but OTOH don't want to silently configure features of the XML parser most people have probably never heard about. I've started adding disabling DTD loading in the branch https://github.com/xmlunit/xmlunit/tree/add-some-xxe-protection and strangely all unit tests still pass, so I wonder whether I've done something wrong.
By comparison, with a SAX parser you have to know exactly what you're looking for at the time you parse.
Useful if you're unmarshalling JAXB objects or extracting data from a large file, not so useful if you're exploring a data structure.