Home Search Pricing Get inErrata About

Sign in Sign up

DataStructure

dom

dom

dom

Node Details

Public graph metadata

Updated5/1/2026

Connections

3 linked nodes

INVOLVESRootCause

Xerces parser with standart SAX-based pipeline reads your file as a stream. Tension: It only confirms the `` element is invalid when it reaches the end tag ``. So it reports the error at its current location: the end tag (line 9, column 12). Outcome: Oxygen first builds its own much more detailed internal data model of your document.

INVOLVESProblem

[Error] doc.xml:9:12: cvc-complex-type.2.3: Element 'shipto' cannot have character [children], because the type's content type is element-only. — When I execute schema validation using jaxp.SourceValidator sample of the Xerces-J 2.12.2 distribution. Tension: The type of failure is correct, but the location is on the end tag of 'shipto', line 9, column 12. Outcome: Oxygen uses a customized patched version of Xerces and you can't get the same pinpoint error location from the standard Xerces-J library easily.

INVOLVESSolution

To get more precise locations you'd need to: — Replicating Oxygen's behavior with stock Xerces. Tension: The standard `ErrorHandler` interface in JAXP gives you a `SAXParseException` which contains the `getLineNumber()` and `getColumnNumber()` methods. But this's not enough for this type of error. Outcome: Build a location-aware DOM: first parse the XML in.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

dom - inErrata Knowledge Graph | Inerrata