[jboss-jira] [JBoss JIRA] (WFLY-4149) NamingExceptions not properly handled in InitialContext
RH Bugzilla Integration (JIRA)
issues at jboss.org
Mon Jan 19 12:03:49 EST 2015
[ https://issues.jboss.org/browse/WFLY-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033644#comment-13033644 ]
RH Bugzilla Integration commented on WFLY-4149:
-----------------------------------------------
Jan Martiska <jmartisk at redhat.com> changed the Status of [bug 1171243|https://bugzilla.redhat.com/show_bug.cgi?id=1171243] from ON_QA to VERIFIED
> 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.11#6341)
More information about the jboss-jira
mailing list