#861
  • Created on
    2011-01-24 23:57
  • Reported by
    fanf
  • Status
    Fixed
  • Priority
    Low (4)
  • Assigned to
    dpp
  • Milestone
    2.3-RC1
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

ExceptionChain or getCause for Failure

For debugging/logging purpose, I commonly have to find the root cause of a Failure.
When it is an exception and the failure is composed, I miss something like "messageChain" but which allows to find the deeper exception of the composition.

It is rather easy to build the list of Failure in a composed Failure with a little recursion and then find the first exception (if exists), but it would be even cooler if it was a built-in method of Failure, something like:

Failure#exceptionChain : List[Throwable] (deeper first ?)
or
Failure#getCause : Option[Throwable] (only the deepest ?) 
or even
Failure#failureChain : Seq[Failure] (deepest first ?)



See https://groups.google.com/d/topic/liftweb/CkdugELLGJA/discussion
User picture
  on 2011-01-25 00:00 *
By dpp
Assigned to set to dpp
Milestone set to 2.3-RC1
Status changed from New to Accepted
User picture
  on 2011-01-26 14:33 *
By Christoph Knabe
For consistency with the Java class Throwable I would prefer, that a method getCause will return only the immediate cause of a Failure, but not the deepest one.
For the latter I would suggest a name like getOriginalCause or getDeepestCause.
User picture
  on 2011-02-16 01:31 *
By dpp
Status changed from Accepted to Fixed
(In revision:18d569232ef2c75d135fd7dad73847bb842fe188) Closes #856. Makes Box a first class citizen in Loggable
Closes #861. Additional goodies for getting Exceptions from Failure
Ref #886. Makes user agent stuff more flexible

Branch: master