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

Refactor JGroups protocol stack creation

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • 10.1.0.Final
    • Clustering
    • None

    Description

      Currently, JGroups protocols are represented using a generic resource. This is done so that the JGroups configurator can create the protocol stack from a generic set of properties.

      This has proven to be very limiting - especially when specific protocols need to reference specific capabilities. e.g. JDBC-based protocols, security protocols, etc.

      These type of protocols should be created programmatically, and have any dependent capabilities applied directly, instead of via string-based properties.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBEAP-11129 AUTH protocol should obtain X509 certificate from an Elytron capability

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-6814 Add outbound-socket-binding capability reference support for TCPPING.initial_hosts

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-8002 Encrypt protocols should obtain keys from an Elytron KeyStore capability

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-8019 AUTH protocol should obtain X509 certificate from an Elytron capability

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-8020 SASL protocol should be configured from Elytron capabilities

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: