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-29) getPath needs improved exception cases
Date Wed, 29 May 2013 20:38:21 GMT

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

Jordan Zimmerman resolved CURATOR-29.
-------------------------------------

    Resolution: Won't Fix

This is a stylistic issue. Please bring this up on the dev list. I don't like specific exceptions.
There shouldn't be a need to examine an exception. If an exception is thrown you are in a
bad state.
                
> getPath needs improved exception cases
> --------------------------------------
>
>                 Key: CURATOR-29
>                 URL: https://issues.apache.org/jira/browse/CURATOR-29
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.0-incubating
>            Reporter: John Vines
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>
> https://github.com/Netflix/curator/issues/13
> Known issue, before was dismissed, but I think there is room for improvement. A generic
exception provides very little recourse for good error handling without trudging through the
code to determine real error cases.

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

Mime
View raw message