> Subject: Re: [dom4j-user] W3C DOM interfaces
>
> Peter,
>
> Take a look at DOMReader and DOMWriter.
>
> steve
>
Steve,
That's what we've been using so far and has been working fine with a few
issues.
We use:
DOMWriter dw = new DOMWriter();
org.w3c.dom.Document w3cDoc = dw.write(doc);
The issues we are running into are:
There is some (relatively) considerable processing overhead in the
DOMWriter - creating a W3C DOM Document takes longer than either
creating the doc from scratch in code or parsing the doc from a file.
The timings I've used for testing DOMWriter use the simple performance
testing code on the dom4j website. I've made an equivalent EXML version
for our own testing and the createW3CDOM method basically becomes a
no-op as it's already a DOM document.
In our testing we get: (all times in millis)
100 Elements --------------------
Creation time : 59.4
W3C Creation time for :1359
DOM4J File write time :344
Parsing time for :346.9
The other issue is purely the convenience of not having to go through
that step each of extra code compared to the way Electric XML does it by
implementing the DOM interfaces directly.
Also I could well have stuffed something up with my testing code or
general understanding of how these work and would welcome and hints on
possibilities in increasing the performance of writing the DOM.
peter w.
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user
