The JDOM Configuration classes (mostly the Proxy) are
not well compatible with namespace-based schemas.
The
current JDOMConfigurationProxy implementation (1.44)
only checks for non-namespaced elements.
I have attached a version which handles reading of
name-spaced child elements through brute-force
searching (still not complete for array based, but the
same methodology will apply).
The bigger problem is when a user wishes to udpate or
add a node. Carbon has no way to easily tell what name
space the new node should be written too. It will
generally be okay to use the parent node's namespace,
but not always. This is especially true in the case of
nested configurations which would important schemas
from other spaces.
Scratchy #511
JDOMConfigurationProxy.java