IBM Developer Works has released an article discussing (trashing) JAXP.
http://www.ibm.com/developerworks/xml/library/x-xjavaforum4.html?ca=drs-
I don't think I really agree with the author's 'reasoning' ...
He states in the first part of the article that: "JAXP was initially intended merely to provide convenience and vendor-neutrality to SAX and DOM". The strange thing is that this is exactly what it is currently, except for adding Schema validation functionality (which is quite handy), the DOM and SAX functionality has hardly changed from the initial release.
In the second part the author writes: "Talking about a ContentHandler or a DOMImplementation is largely a thing for the past, or at least relegated to pretty high-end Java and XML programmers". This is also not the case, JAXP does not wrap any DOM or SAX functionality, the user still needs to create a ContentHandler to be able to process SAX events and the user will still need to know about Document, Element and Attr nodes.
The conclusion is as expected: "I think that JAXP has obscured the value of learning SAX and the DOM APIs on their own, without really providing significant value in return."
Even though I don't think JAXP is perfect and the API might not always have been defined at the right level (although I cannot think of any examples), the arguments that the author made to reach this conclusion are simply wrong.
Labels: article, Brett D McLaughlin, jaxp, xml
0 Comments:
Post a Comment
<< Home