handling exceptions

[gaurav v bagga]

hi all,
i am having few methods they all throw few common exceptions

method1 throws a,b,c
method 2 throws a,b,c
method3 throws a,b .......

can i some how make it throw only one exception which will take care
of res all others

like

method1 throws foo
method2 throws foo

and foo encapsulates all a,b,c

something like that possible..

a,b,c mainly i have are

SQLException, InstantiationException, IllegalAccessException,
ClassNotFoundException

regards
gaurav

 

[Remon van Vliet]

hi all,
i am having few methods they all throw few common exceptions

method1 throws a,b,c
method 2 throws a,b,c
method3 throws a,b .......

can i some how make it throw only one exception which will take care
of res all others

like

method1 throws foo
method2 throws foo

and foo encapsulates all a,b,c

something like that possible..

a,b,c mainly i have are

SQLException, InstantiationException, IllegalAccessException,
ClassNotFoundException

regards
gaurav

There is such an encapsulating exception type, namely Exception. You could
catch Exception and where needed doing instanceof checks inside the catch to
determine which exception was thrown. That will not win points for clarity
and style but may be enough for what you need if you only require a
"something i dont care about went wrong" signal.

Remon

 

[Patricia Shanahan]

hi all,
i am having few methods they all throw few common exceptions

method1 throws a,b,c
method 2 throws a,b,c
method3 throws a,b .......

can i some how make it throw only one exception which will take care
of res all others

like

method1 throws foo
method2 throws foo

and foo encapsulates all a,b,c

something like that possible..

a,b,c mainly i have are

SQLException, InstantiationException, IllegalAccessException,
ClassNotFoundException

regards
gaurav

You can do this by having foo extend Exception, but only use the
constructors that have a Throwable cause parameter.

However, it is desirable to make sure you provide enough granularity in
foo and it subclasses to allow reasonable try-catch structure. It looks
to me as though you have two major clusters of potential exceptions,
database problems and class management problem. I would put those in
separate subclasses of foo, so that a caller can catch them separately.

Patricia