a better mousetrap, and the world will
a path to your door."
provide a complete, Java-based solution for accessing, manipulating,
and outputting XML data from Java code. Read more about our project
2.0.5 is available! This is a recommended upgrade for anyone still using
JDOM 1.1.3 or earlier, and using Java5 or later. JDOM 2.0.5 contains a few fixes:
Get JDOM Here!
JDOM 2.x versions are a significant reworking of the JDOM API to enhance it with Generics, and
other Java Language features introduced with Java 5. JDOM 2.x is fully supported for
use with Java 6 or Java 7, and is also compatible with Java 5 with a few restrictions.
See the full
Statement on Supported Versions and Dependencies
To facilitate the deployment of JDOM 2.x, the entire JDOM package has been renamed.
If you are migrating to JDOM 2.x from previous JDOM versions you will need to change
your package imports from org.jdom.* to org.jdom2.*
JDOM 1.x to JDOM 2.x migration guide is available.
JDOM 1.x versions are operating in maintenance mode only and only
bug fixes will be considered for future 1.x releases. The only reason to continue using
JDOM 1.x is for compatibility with older Java versions (back to Java 1.2).
New features are being considered for JDOM2 though. If you want to be
involved, or have suggestions or questions, please write in to the
mailing list and check out the
Get JDOM Here!
- Fixes Issue 106 - Uses different methods on StAX Stream output to ensure that Namespace URI's are prefixed correctly.
- Fixes Issue 111 - Improve documentation for SAXBuilder.build(String) so that it is more obvious that the String is not actual XML values, but a URI.
- Fixes Issue 112 - Improves performance of SAXBuilder when there are large ( greater than 1KB ) text sections in the input XML.
- Fixes Issue 113 - Compile (and test) against Jaxen 1.1.6
- Fixes Issue 114 - Setting the Line Separator for JDOM would not work from System.properties().
- Fixes Issue 115 - Correctly set the 'xmlns' prefix and URI for Namespace declarations in DOMOutputter.
- Fixes Issue 116 - JDOM 1.x uses an iterator to output XML child content, modify JDOM 2.x to do the same.
We've succeeded in our mission with an API that's been through years
of design and development and a codebase that is rock solid.
JSR-102? That's a good question. It hasn't been a priority for
us. We seem to be doing pretty well on our own, it turns out.
If you are wondering
what Jason has been doing lately, he's working on
MarkMail. It's a searchable email archive system.
You can try searching the JDOM lists at
2.0.x versions are out, and work is starting on identifying what new features can be added
to a future 2.1.x release series. If you have comments, questions, or suggestions for something
that is, or should be, in a 2.1.x release, please write in to
jdom-interest. Current features being considered are improved
XPath support (XPath 2.0) and updated XSLT processing, and also an extended StAX Handling API.