[jboss-jira] [JBoss JIRA] (WFLY-4149) NamingExceptions not properly handled in InitialContext

RH Bugzilla Integration (JIRA) issues at jboss.org
Fri Dec 5 12:45:39 EST 2014


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

RH Bugzilla Integration commented on WFLY-4149:
-----------------------------------------------

Brad Maxwell <bmaxwell at redhat.com> changed the Status of [bug 1171243|https://bugzilla.redhat.com/show_bug.cgi?id=1171243] from NEW to POST

> NamingExceptions not properly handled in InitialContext
> -------------------------------------------------------
>
>                 Key: WFLY-4149
>                 URL: https://issues.jboss.org/browse/WFLY-4149
>             Project: WildFly
>          Issue Type: Bug
>          Components: Naming
>            Reporter: David Lloyd
>            Assignee: Eduardo Martins
>             Fix For: 9.0.0.Beta1
>
>
> The change in https://github.com/jbossas/jboss-eap/commit/db525bf1d90a40eb909c8f915fca787d55f4e7e5#diff-833175ffb151a3398216d6422dadeeeeR112 catches all Exception and rewraps them with NamingException.  This behavior is undesirable if the original exception was already a NamingException.  Catch and re-throw that exception type as-is before wrapping other exceptions.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the jboss-jira mailing list