XOM API for Processing XML with Java

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

At 6:24 PM -0500 7/20/03, Bradley S. Huffman wrote:

> XOMParseException. With XOM in the name it's highly unlikely another
> conflict will ever occur.

So I call for a vote and the write-in candidate wins. I don't know. I 
may have to use my veto power on this one. XOMParseException feels 
wrong to me. One reason we have packages is so we don't have to write 
XOMParseException, XOMDocument, XOMNode, XOMText, etc.

Plus, if there's a XOMParseException, I'd sort of expect to see a 
generic XOMException superclass that covers all the exceptions in 
XOM, but I can't really have that because of the distinction between 
checked and runtime exceptions.

For the moment I'm leaning toward XMLParseException. Then again maybe 
I shouldn't do anything at all. This is not the only potential 
conflict. Besides the obvious conflicts with DOM, others include

javax.swing.text.Document
javax.naming.directory.Attribute

ParseException is the only conflict with the core Java classes though.
--

  Elliotte Rusty Harold
  elharo AT metalab.unc.edu
  Processing XML with Java (Addison-Wesley, 2002)
  http://www.cafeconleche.org/books/xmljava
  http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA