[
https://issues.apache.org/jira/browse/ZOOKEEPER-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181743#comment-15181743
]
Flavio Junqueira commented on ZOOKEEPER-2154:
---------------------------------------------
[~surendrasingh] thanks for the patch. Since we already throw that same
exception in the default case of the switch, would it make sense to not
duplicate? I was thinking that we could have a code for NULL, check for null,
and assign code to NULL. Another idea is to use {{assert code != null;}}.
Let me know what you think, please.
> NPE in KeeperException
> ----------------------
>
> Key: ZOOKEEPER-2154
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2154
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.6
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2154.patch
>
>
> KeeperException should handle exception is code is null...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
