You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2014/08/01 22:45:39 UTC

[jira] [Reopened] (CURATOR-135) API Cleanup: Avoid throwing Exception

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

Jordan Zimmerman reopened CURATOR-135:
--------------------------------------


Leave open so that the community can vote on this. My personal vote is a huge -1 binding. If I had to do it over again I'd getting rid of checked exceptions altogether.

> API Cleanup: Avoid throwing Exception
> -------------------------------------
>
>                 Key: CURATOR-135
>                 URL: https://issues.apache.org/jira/browse/CURATOR-135
>             Project: Apache Curator
>          Issue Type: Improvement
>            Reporter: Mike Drob
>            Assignee: Jordan Zimmerman
>
> It would be nice if the API did not throw Exception in so many places and threw the more specific subclasses instead. We should scrub the API to improve the method signatures, possibly creating sub-tasks to do so on a module-by-module (or more granular) basis.



--
This message was sent by Atlassian JIRA
(v6.2#6252)