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

Subsystem iiop-openjdk should define port bindings in default configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 10.0.0.CR2
    • 10.0.0.Beta1
    • IIOP
    • None

    Description

      Default configuration that is shipped with EAP/WFLY for iiop-openjdk subsystem does not contain port binding. This could be a bit confusing for users when looking on configuration file and if they check for strings/ports iiop and iiop-ssl they are not mentioned in configuration file. Course the name suggests what they are for but I think that configuration file should avoid such implicit usage which came from default values settings.

      JacORB subsystem in EAP 6.4 looked like

              <subsystem xmlns="urn:jboss:domain:jacorb:1.4">
            <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
                <initializers transactions="spec" security="identity"/>
            </orb>
        </subsystem>

      I think that the IIOP OpenJDK subsystem should define the socket binding as well. I mean instead of

              <subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0">
            <initializers transactions="spec" security="identity"/>
        </subsystem>

      the default configuration could be

              <subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0">
            <orb ssl-socket-binding=\"iiop-ssl\" socket-binding=\"iiop\"/>
            <initializers transactions="spec" security="identity"/>
        </subsystem>

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-788 Subsystem iiop-openjdk should define port bindings in default configuration

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: