ExceptionEvent.getCause() returns Throwable. Why ?

[Marc-André Laverdière]

You are right. Looks like I haven't been sleeping enough lately :(

The only example I see that could make sense is IF (big if) you have a
lazy loaded configuration file. Your handler requests a config
parameter, your API does the loading, the file is not there... BAM:
ConfigurationError.
Granted, your API may throw an exception, but mine throws an error :(

Its not even a great example, but that's the best I can think of. Not
sure it justifies using Throwable.

Marc-André LAVERDIÈRE
"Perseverance must finish its work so that you may be mature and
complete, not lacking anything." -James 1:4
mlaverd.theunixplace.com/blog

 /"\
 \ /    ASCII Ribbon Campaign
  X      against HTML e-mail
 / \



2010/7/16 Tchoum <happytchoum at hotmail.com>:
>
> Hi,
>
> All the exceptions that you name are under the Exception. The Error like
> OutOfMemoryError are under Throwable and should most likely not handled as
> they are quite bad if it happens.
>
> Let me know what you think,
>
> PL
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/ExceptionEvent-getCause-returns-Throwable-Why-tp5295752p5300008.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>