[
https://issues.apache.org/jira/browse/BLUR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gagan Deep Juneja updated BLUR-167:
-----------------------------------
Attachment: 0001-BLUR-ID-167-added-new-exception-for-Bad-Connections.patch
I have added new runtime exception BadConnectionException and handled the same
in Main.java in blur shell project. Please have a look and let me know your
feedback. I made this exception runtime in order to avoid unnecessary catch
statements. One more thing in case of this exception should we exit the shell
also or not?
> 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
>
> Attachments:
> 0001-BLUR-ID-167-added-new-exception-for-Bad-Connections.patch
>
>
> 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
