XOM API for Processing XML with Java

[Elliotte Rusty Harold <elharo AT metalab.unc.edu>]

At 1:48 AM -0500 2/5/04, Sandy Mustard wrote:
> I use XOM because it is easy to program.  I don't see why I can't 
> use it in an EJB.  I don't want to have my developers using two 
> different methods of accessing XML.

I don't see why you can't use it with EJB either. It has not yet been 
proven to my satisfaction that it is necessary for the XOM classes to 
be Serializable in order to be used with EJB. So far, there's one 
report from an EJB novice who says he thinks he needs this, but he 
isn't really sure. Three separate work-arounds have been suggested 
that don't require marking the XOM classes Serializable. Unless 
there's more convincing evidence that EJB actually requires XOM 
classes to be Serializable, they won't be.

> Making XOM serializable can be as simple as adding "implements Serializable".

If only it were that simple. It's not. Implementing Serializable is a 
major undertaking that requires significant foresight, planning, and 
design. Unless there's clear evidence that object serialization is 
necessary for a significant class of users, I'm not going to 
complexify XOM by adding it.

--

  Elliotte Rusty Harold
  elharo AT metalab.unc.edu
  Effective XML (Addison-Wesley, 2003)
  http://www.cafeconleche.org/books/effectivexml
  http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA