Andrus Adamchik wrote:
> Kevin, et al.
>
> Here is an XMLDecoder patch that took me about 20 minutes to create. It
> replaces JDOM with DOM. (OK, I hit Ctrl-F, so it has more changes than
> there really is). Also I cheated a bit - I commented out parts that
> required changing MappingUtils ... so it passes all unit tests except
> those that involve mapping. It should be similarly easy to port
> encoder, just need to borrow pretty-print code from Xerces examples or
> something.
Well, that's certainly good to hear. I did expect it to take much
longer than that.
>
> One of the caveats is that missing attribute values are returned as ""
> by DOM, while they are returned as "null" from JDOM. Actually it turned
> out that it saved some code as we no longer need to do null checking :-).
>
> I volunteer to proceed with the rest of the port, just wanted to run it
> by you first. Any comments?
Looks good. Your XMLUtil class is a nice wrapper. Given this, I'd say
go with it. JDOM apparantly wasn't gaining us much as I thought :-P
-- Kevin
This archive was generated by hypermail 2.0.0 : Fri Oct 14 2005 - 17:54:50 EDT