Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] How to make the object of nu.xom.Document may toserialize ?

xom-interest AT

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Tatu Saloranta <cowtowncoder AT>
  • To: Steve Loughran <steve.loughran AT>
  • Cc: xom-interest AT
  • Subject: Re: [XOM-interest] How to make the object of nu.xom.Document may toserialize ?
  • Date: Sun, 9 Dec 2007 17:40:37 -0800 (PST)

--- Steve Loughran <steve.loughran AT> wrote:

> On Dec 5, 2007 11:39 AM, Michael Kay
> <mike AT> wrote:
> > But the best way to serialize a tree
> representation of an XML document is as
> > XML. So Java serialization really isn't
> appropriate.
> Putting aside technical and idelogical purity,
> sometimes its good to
> serialize document trees, as that way you can
> marshall it over RMI
> with ease
> (a) use JDom; this is a supported use case
> (b) subclass nu.xom.Document, implement
> serialize/deserialize code
> that saves the doc to a UTF8 encoding in a byte
> array, and sends that
> over the wire, converting it at the far end .

While this is certainly possible, the question is, why
bother? Serialization to textual xml can be done in
couple of lines of code and results in a byte array
(directly or via ByteArrayOutputStream) easily
transmittable using normal methods, be that sending
via sockets, or even sending over RMI as a byte array.

This method is unlikely to be slower end-to-end than
object-serialization alternatives, given how fast xml
parsing and serialization is, and the overhead of
default Java object serialization.

-+ Tatu +-

Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

Archive powered by MHonArc 2.6.24.

Top of Page