Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] Why nu.xom.ParseException?

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: "Bradley S. Huffman" <hip AT cs.okstate.edu>
  • To: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
  • Cc: xom-interest AT lists.ibiblio.org
  • Subject: Re: [XOM-interest] Why nu.xom.ParseException?
  • Date: Thu, 03 Jul 2003 22:13:38 -0500

Elliotte Rusty Harold writes:

> At 3:56 PM -0500 7/3/03, Kevin Herrboldt wrote:
> >This is a style question instead of a functional question.
> >
> >I've used java.text.ParseException to indicate similar exceptions in
> >my own code, and it seems like a natural fit. I can see wanting to
> >keep the exception in the nu.xom.* package, but maybe a different
> >name could be considered?
> >
> >It's a minor irritation, but I've got code picking dates out of a
> >XOM document (think DocBook) and using a DateFormat to parse them,
> >which can throw a java.text.ParseException. I can't import both
> >nu.xom.ParseException and java.text.ParseException, so my code gets
> >littered with ugly full-package class references.
>
> OK. I hadn't noticed that myself yet, but I agree it would be nice
> not to needlessly conflict. So what other names do people like?
> XMLParseException? ParseXMLException? Suggestions anyone?

Do you need a ParseException in nu.xom, it doesn't extend any other class
in nu.xom so couldn't you use java.text.ParseException instead?

Brad




Archive powered by MHonArc 2.6.24.

Top of Page