[
Lists Home |
Date Index |
Thread Index
]
Bullard, Claude L (Len) wrote:
> Elliotte, please explain why JAXB 2.0 and Apache Commons Digester
> are improvements with respect to strong typing.
They are improvements because they make the typing weaker. They make it
much easier to tie the XML documents to classes of your choice, with
method invocations, configuration, and initialization that you want to
do. They are much more flexible and much less fixed. (Digester much more
so than JAXB 2.0.)
For Digester, see Herve Agnoux's article (in French)
http://beuss.developpez.com/tutoriels/java/jakarta/commons/digester/
For JAXB 2.0 Kohsuke Kawaguchi has written quite a bit in his blog:
http://weblogs.java.net/blog/kohsuke/
See, in particular,
http://weblogs.java.net/blog/kohsuke/archive/2005/09/using_jaxb_20s.html
"Sometimes when you are binding your own classes to XML, you hit with a
situation where your class representation doesn't quite match what you'd
like to see in the XML. Some other times, some of your classes hit the
limitation in JAXB that the class must have a default constructor.
XmlJavaTypeAdapter is a solution for those problems."
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
|
