Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
5.2.4
-
None
Description
findCause() only works using the cause property, whereas in many cases (older code typically that predates the cause property, introduced in JDK 1.4)) there's an alternate property that stores the actual nested exception.
ExceptionAnalyzer does it correctly, at higher cost (lots of property access to identify the cause).