Web / Apache Axiom Interview questions
What is the difference between Axiom and standard DOM?
The two solve the same broad problem - an in-memory, navigable representation of XML - but make different tradeoffs around when and how much gets built.
| Axiom | DOM |
| Built on StAX (pull); deferred/lazy building | Typically eager; whole tree built up front |
| Custom API, plus an optional org.w3c.dom-compatible mode | Standard W3C API (org.w3c.dom) |
| Native MTOM/binary attachment support | No built-in attachment optimization |
| Purpose-built for SOAP/web-services messaging | General-purpose XML document API |
| Lower memory for large docs, partial access | Higher memory, since everything is materialized |
In practice, Axiom tends to win for high-throughput web-services scenarios, especially with large payloads or attachments where only part of the document is ever inspected, while plain DOM remains attractive when an application needs strict standards compliance or must integrate with libraries that only understand org.w3c.dom types directly.
More Related questions...