ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #xml
StAX provides a low‑memory, event‑driven API while DOM builds a complete in‑memory tree, creating a mismatch when the two are combined at an integration point. Goal: design a pattern that allows StAX to supply parsed fragments to a DOM builder without causing unbounded memory growth, especially for documents exceeding 100 MB. Uncertainty remains about whethe
We run a validation pipeline where a base schema (base.xsd) and a derived XSD 1.1 schema (derived.xsd) coexist. The derived schema uses xs:override to tighten a complexType with an xs:assert , and it also adds a new member to an existing substitution group. Instance documents are produced against derived.xsd, but on a failed deployment we need to re-validate
Goal is to constrain XML documents with namespaces, typed values and co-occurrence rules while keeping validation portable across common XML parsers. DTD is built into XML 1.0 and widely supported, but it lacks namespace awareness and offers only coarse typing. XSD provides typed elements and attributes, occurrence constraints and namespace support, with sch
The rewriteSystem element in OASIS XML Catalogs 1.1 maps a system identifier prefix to a replacement URI, which is useful for redirecting external entity references in a repeatable development environment. When a project combines multiple catalog files through a catalog preference file, delegate entries, or processor-specific catalog chains, the specificatio
XML Schema Validation Overhead in Low-Traffic Java Applications The standard Java XML APIs, such as DocumentBuilderFactory, default to non-validating parsing mode. However, enabling schema validation through setValidating(true) or setSchema(...) introduces an additional validation pass that increases CPU usage and memory consumption. For low-traffic workload
Achieving deterministic XML validation in repeatable CI/CD pipelines requires a choice between embedded xsi:schemaLocation URLs and OASIS XML Catalogs. Using remote URLs allows validators to fetch schemas at runtime, but this introduces non-determinism if the remote schema changes or the network is unavailable. Alternatively, XML Catal map namespace URIs to
java