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

Module org.wildfly.naming does not export JndiPermission

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 10.1.0.CR1, 10.1.0.Final
    • 10.0.0.Final
    • Naming
    • None

    Description

      The new module org.wildfly.naming which contains JndiPermission does not export it. Hence, the module is efficiently useless. Deployments still have to depend on the private org.jboss.as.naming module to get the JndiPermission to work.

      Attachments

        Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-4195 Module org.wildfly.naming does not export JndiPermission

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. WFLY-5810 JNDIPermission is based in a private module

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

                istudens@redhat.com Ivo Studensky
                istudens@redhat.com Ivo Studensky
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: