[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: [SAX] setProperty and exception

• From: "Robert C. Lyons" <boblyons@u...>
• To: Kohsuke KAWAGUCHI <kohsukekawaguchi@y...>, xml-dev@l...
• Date: Fri, 28 Sep 2001 20:20:59 -0400

Based on the following sentence in the description of
the org.xml.sax.SAXNotSupportedException class,
I believe that an XMLReader.setProperty method should
throw a SAXNotSupportedException when the property
name is recognized and supported, but the value is
invalid:

   An XMLReader will throw this exception when it
   recognizes a feature or property identifier, but
   cannot perform the requested operation (setting
   a state or value).

Hope this helps.

Bob

<sig name    = 'Bob Lyons'
     title   = 'B2B Integration Consultant'
     company = 'Unidex, Inc.'
     phone   = '+1-732-975-9877'
     email   = 'boblyons@u...'
     url     = 'http://www.unidex.com/'
     product = 'XML Convert: transforms flat files to XML and vice versa' />

-----Original Message-----

XMLReader#setProperty can throw two types of exceptions. One is
"not-recognized" and the other is "not-supported".

But it seems to me that we need the third "bad-value" exception, which
indicates that the property name is recognized and supported but the
specified value is wrong. (For example, String is passed where Integer
is expected, or 127 was passed where the valid value is between 0 and
100.)

What is the right exception to throw for cases like this?


regards,
----------------------
K.Kawaguchi
E-Mail: kohsukekawaguchi@y...

• Follow-Ups:
  • Re: [SAX] setProperty and exception
    • From: Kohsuke KAWAGUCHI <kohsukekawaguchi@y...>

• References:
  • [SAX] setProperty and exception
    • From: Kohsuke KAWAGUCHI <kohsukekawaguchi@y...>

• Prev by Date: [SAX] setProperty and exception
• Next by Date: Re: Ambiguous Content Model
• Previous by thread: [SAX] setProperty and exception
• Next by thread: Re: [SAX] setProperty and exception
• Index(es):
  • Date
  • Thread