You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/02/13 16:49:56 UTC

[jira] [Closed] (BOOKKEEPER-394) CompositeException message is not useful

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly closed BOOKKEEPER-394.
---------------------------------

    
> CompositeException message is not useful
> ----------------------------------------
>
>                 Key: BOOKKEEPER-394
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-394
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>            Priority: Minor
>             Fix For: 4.2.0
>
>         Attachments: 394.diff
>
>
> Exceptions logged via slf4j don't actually have their toString method called, so the current behaviour of overriding toString for CompositeException is rarely/never triggered in client code.
> Composing a better `message` field for CompositeException would make it loggable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira