curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CURATOR-135) API Cleanup: Avoid throwing Exception
Date Fri, 01 Aug 2014 19:15:39 GMT

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

Jordan Zimmerman resolved CURATOR-135.
--------------------------------------

    Resolution: Not a Problem

This is a core design decision of Curator. Exception is always thrown.

> 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)

Mime
View raw message