This is an AMP version of the article, its original content can be found here.
JAXB Is Doing It Wrong; Try Xembly
JAXB is a 10-year-old Java technology that allows us to convert a Java object into an XML document (marshalling) and back (unmarshalling). This technology is based on setters and getters and, in my opinion, violates key principles of object-oriented programming by turning objects into passive data structures. I would recommend you use Xembly instead for marshalling Java objects into XML documents.
This is how JAXB marshalling works. Say you have a
Book class that needs to be
marshalled into an XML document. You have to create getters and annotate them:
Then you create a marshaller and ask it to convert an instance of class
Book into XML:
You should be expecting something like this in the output:
So what's wrong with it? Pretty much the same thing that's wrong with object-relational mapping, which is explained in ORM Is an Offensive Anti-Pattern. JAXB is treating an object as a bag of data, extracting the data and converting it into XML the way JAXB wants. The object has no control over this process. Therefore an object is not an object anymore but rather a passive bag of data.
An ideal approach would be to redesign our class
Book this way:
However, there are a few problems with this approach. First of all, there's
massive code duplication. Building an XML document is a rather verbose
process in Java. If every class had to re-implement it in its
toXML() method, we would have a big problem with duplicate code.
The second problem is that we don't know exactly what type of wrapping
our XML document should be delivered in. It may be a
String or an
or maybe an instance of
org.w3c.dom.Document. Making many
in each object would definitely be a disaster.
Xembly provides a solution. As I've
mentioned before, it is
an imperative language for XML constructions and manipulations. Here is
how we can implement our
Book object with the help of Xembly:
Now, in order to build an XML document, we should use this code outside the object:
class will convert Xembly directives into an XML document.
The beauty of this solution is that the internals of the object are not exposed via getters and the object is fully in charge of the XML marshalling process. In addition, the complexity of these directives may be very high—much higher than the rather cumbersome annotations of JAXB.
Xembly is an open-source project, so feel free to submit your questions or corrections to GitHub.