-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
P4
-
Affects Version/s: 6
-
Component/s: client-libs
-
x86
-
windows_xp
There's two places in the code where TransferHandler does something like:
try {
// call public/protected TransferHandler method
} catch (RuntimeException e) {}
This is bad because it hides an exception the developer likely needs to know about. For example, how would a developer know if they were doing a bogus cast that triggered a ClassCastException?
try {
// call public/protected TransferHandler method
} catch (RuntimeException e) {}
This is bad because it hides an exception the developer likely needs to know about. For example, how would a developer know if they were doing a bogus cast that triggered a ClassCastException?