[
https://issues.apache.org/jira/browse/CURATOR-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186233#comment-15186233
]
ASF GitHub Bot commented on CURATOR-306:
----------------------------------------
Github user cammckenzie commented on the pull request:
https://github.com/apache/curator/pull/139#issuecomment-194051764
Looks good to me. It does make me appreciate how much duplicate code there
is in all of the builder classes though. We should probably look at
rationalising that at some point.
> Background operations would benefit from an optional error handler
> ------------------------------------------------------------------
>
> Key: CURATOR-306
> URL: https://issues.apache.org/jira/browse/CURATOR-306
> Project: Apache Curator
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 3.1.0, 2.10.0
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Priority: Minor
> Fix For: 2.10.1, 3.1.1
>
>
> If an exception is thrown during processing of a background operation in the
> Framework, the error eventually goes to the global UnhandledErrorListener.
> This makes correlating the error with the site of the error difficult. It
> would be nice to have a call-specific error handler that is called in this
> case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
