Pitfall - Directly subclassing Throwable

suggest change

Throwable has two direct subclasses, Exception and Error. While it’s possible to create a new class that extends Throwable directly, this is inadvisable as many applications assume only Exception and Error exist.

More to the point there is no practical benefit to directly subclassing Throwable, as the resulting class is, in effect, simply a checked exception. Subclassing Exception instead will result in the same behavior, but will more clearly convey your intent.

Feedback about page:

Feedback:
Optional: your email if you want me to get back to you:


Pitfalls - exceptions:
* Pitfall - Directly subclassing Throwable

Table Of Contents
8 Arrays
10 Maps
11 Strings
25 JAXB
29 Enums
32 Audio
41 Scanner
63 Logging
75 Lists
78 Sets
89 JAX-WS
96 XJC
98 Process
106 Modules
107 Pitfalls - exceptions
114 Applets
122 JNDI
139 JavaBean
141 Literals
144 Packages
150 JMX
153 JShell
159 Sockets
167 Enum Map
175 Hashtable
177 SortedMap