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

Request for try{}catch

From: Alexandre Rafalovitch <alex@access.com.au>
Date: Tue, 15 Oct 1996 20:38:05 +1000
Message-Id: <v03007800ae8914c5619a@[203.18.229.116]>
To: www-jigsaw@w3.org
I just ran into the problem that made me wish Jigsaw had a bit more
protection against the programmer.

I will give an easy example.

I created the class based on the other file. It compiled fine, but when I
tried to add it to Jigsaw, it bombed out.

Looking through the trace, I realized that the mistake was mine. I forgot
to change the name of the file in Class.getForName() so was getting
non-existing class. That caused Jigsaw to bomb out without any way to save
data or anything else.

It would be very nice if the process of creating new resource had a big
try/catch close and used that to see if resource creation would bomb out
and if it will, refuse creation of resource the same way it does if it just
can't find it.

Alex.

alex@access.com.au
Received on Tuesday, 15 October 1996 06:42:20 GMT

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