[
https://issues.apache.org/jira/browse/BOOKKEEPER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450300#comment-13450300
]
Hudson commented on BOOKKEEPER-394:
-----------------------------------
Integrated in bookkeeper-trunk #694 (See
[https://builds.apache.org/job/bookkeeper-trunk/694/])
BOOKKEEPER-394: CompositeException message is not useful (Stu Hood via
sijie) (Revision 1381848)
Result = SUCCESS
sijie :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/hedwig-protocol/src/main/java/org/apache/hedwig/exceptions/PubSubException.java
> 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
