[
https://issues.apache.org/jira/browse/BLUR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713580#comment-13713580
]
Aaron McCurry commented on BLUR-167:
------------------------------------
That it probably the simplest way to check. I wonder if the BlurClient code
and the BlurManager should throw a not connected exception instead of a
BlurException. Perhaps that would make dealing with clients not being
connected easier.
Aaron
> Check connection in shell make and create a nice error message
> --------------------------------------------------------------
>
> Key: BLUR-167
> URL: https://issues.apache.org/jira/browse/BLUR-167
> Project: Apache Blur
> Issue Type: Bug
> Components: Blur
> Affects Versions: 0.2.0
> Reporter: Aaron McCurry
> Fix For: 0.2.0
>
>
> Check the connection in shell when initially connection and if the connection
> can not be made emit a nice error message instead of stack trace.
--
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
