Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4149

NamingExceptions not properly handled in InitialContext

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.0.Beta1
    • None
    • Naming
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              emartins@redhat.com Eduardo Martins
              dlloyd@redhat.com David Lloyd
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: