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

Naming subsystem does not expose a proper capability contract

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • 10.1.0.Final
    • Naming
    • None

    Description

      Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem.

      Attachments

        Issue Links

          blocks

          Requirement - Used for conducting internal reviews of our products and process with 3rd party auditors JBEAP-7732 [DOC RFE] Domain Fault Tolerance

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-6069 Naming subsystem does not expose a proper capability contract

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: