[jboss-jira] [JBoss JIRA] (WFLY-2839) Remote Naming communication exception should be thrown on ConnectException

[Brad Maxwell (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12940311#comment-12940311 ] 

Brad Maxwell edited comment on WFLY-2839 at 1/30/14 3:05 PM:
-------------------------------------------------------------

Resolved in JBoss Remote Naming 2.0.0 Final & Wildfly fixed version will be via https://issues.jboss.org/browse/WFLY-2849
                
      was (Author: bmaxwell):
    Resolved in JBoss Remote Naming 2.0.0 Final
                  
> Remote Naming communication exception should be thrown on ConnectException
> --------------------------------------------------------------------------
>
>                 Key: WFLY-2839
>                 URL: https://issues.jboss.org/browse/WFLY-2839
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Naming
>    Affects Versions: 8.0.0.CR1
>            Reporter: Brad Maxwell
>            Assignee: Brad Maxwell
>
> Remote Naming communication exception should be thrown on ConnectException, a remoting bug fix showed that a ConnectException can be thrown to remoting and we should throw this as a CommunicationException instead of generic NamingException.  This is related to WFLY-2198

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