XOM API for Processing XML with Java

[Nils_Kilden-Pedersen AT Countrywide.Com]

Serializable is mostly used in distributed computing, and since you're 
using JMS, that's what you're doing too.
In any kind of distributed environment, you should want to limit you 
dependencies and increase your interoperability. Forcing the receiver to 
use XOM is, IMHO, bad distributed design, considering the nature of XML.
Is parsing it twice really a performance issue? More than the network 
latency itself? Do yourself a favor and lose the XOM dependency.

Nils

xom-interest-bounces AT lists.ibiblio.org wrote on 02/19/2004 11:41:24 AM:

> XOM users,
>   Okay, read the "java rules" section of the "what's
> wrong" presentation. So, no XOM classes are
> serializable. My problem is one of avoiding parsing a
> document more than once. When I was using DOM (yuck!) I
> could do many things with my DOM objects such as hang
> them on a JNDI tree and retrieve them later, pass them
> in JMS messages as Object Messages and other niceties
> that come with being serializable. I'll find a way
> around this but I would still like to understand the
> reasons for not implementing serializable? 
> 
> Thanks,
>   Brian
> 
> Brian Sam-Bodden
> President & Chief Software Architect
> Integrallis Software, LLC.
> http://www.integrallis.com
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
>