Apache Xerces2 J

14 years later after my last comment on this issue.... mmazari thanks for the interest in this discussion ! It's hard to contribute fixes to the Xerces project in general, it's not like you can open a pull request with a signoff like in most open Read more

tkrammer/radu_coravu, the provided solutions work fine. However, I have the following concerns:  The provided solution loads all entities into the entity manager each time. In many applications, thousands of entities are present, but only a few are Read more

Entity resolution does not work with DTD grammar caching resolved

Adding an automatic module name makes the xercesImpl.jar usable in JPMS enabled builds without affecting non-JPMS builds. Only a single line in MANIFEST.MF is needed: Automatic-Module-Name: org.apache.xerces.impl     For ultimate compatibility Read more

Implementation for XML DOM documents, a new method 'isEqualNodeWithQName' similar to 'isEqualNode' to compare two XML element nodes

There's a need for XalanJ's XPath 3.1 fn:deep-equal's method implementation, to have XercesJ's java class org.apache.xerces.dom.ElementImpl provide a new method (with name like 'isEqualNodeWithQName'), that can check equality of two XML element nodes Read more

There's a need for XalanJ's XPath 3.1 fn:deep-equal's method implementation, to have a XercesJ's java class org.apache.xerces.dom.ElementImpl provide a new method (with name like 'isEqualNodeWithQName'), that can check equality of two XML element Read more

Unfortunately https://blogs.securiteam.com/index.php/archives/3271 is no longer up (and not available on archive.org), but the discussion in https://github.com/jeremylong/DependencyCheck/issues/4614 suggests this may have to do with XMLEntityManager.setupCurrentEntity() Read more

CVE-2017-10355

improvements to xercesj xml schema 1.1 build implementation