W3C home > Mailing lists > Public > www-jigsaw@w3.org > September to October 1996


From: Dave Makower <davemak@pencom.com>
Date: Thu, 19 Sep 1996 12:21:02 -0400 (EDT)
Message-Id: <v01540b03ae66e8103af4@[]>
To: www-jigsaw@w3.org
From what I can tell from some out-of-sync doc comments in the Jigsaw code,
it looks like the code for AttributeHolder.initialize() used to throw
AttributeHolderInitException, but has been changed to throw no exceptions.
I think it might have been better to allow for such an exception to be

I am trying to create a subclass of FilteredResource that may need to throw
an exception if it isn't initialized properly.  The way initialize() is
declared now, I can't do that.  I think it makes sense for an
AttributeHolder to be responsible for detecting when it receives
inappropriate initialization parameters, but for the initializing object to
be responsible for handling that exception appropriately.

Sounds like a job for Java's exception-handling mechanism, yes?

|    Dave Makower     |    davemak@pencom.com   |   WWW Specialist    |
|     Co-author of "Java Programming Basics" (Henry Holt/MIS:Press)   |
|                 http://www.pencom.com/javabasics/                   |
|   Pencom Web Works               |   (212) 513-7777   voice         |
|   Pencom Systems Inc.            |   (212) 513-1975   fax           |
|   40 Fulton St.                  |                                  |
|   New York, NY  10038            |   http://www.pencom.com/         |
Received on Thursday, 19 September 1996 12:19:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:25 GMT