Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-25629

Empty optional field for config property for socket bindings causes null in config

XMLWordPrintable

      On Socket bindings configuration screens, when one leaves the field for optional property for a port, the generated config contains nulls:

          <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
              <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
              <socket-binding name="http" port="${null:8080}"/>
              <socket-binding name="https" port="${jboss.https.port:8443}"/>
              <socket-binding name="iiop" interface="unsecure" port="${null:3528}"/>
              <socket-binding name="iiop-ssl" interface="unsecure" port="${null:3529}"/>
              <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
              <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
              <socket-binding name="txn-recovery-environment" port="${null:4712}"/>
              <socket-binding name="txn-status-manager" port="${null:4713}"/>
              <outbound-socket-binding name="mail-smtp">
                  <remote-destination host="${jboss.mail.server.host:localhost}" port="${jboss.mail.server.port:25}"/>
              </outbound-socket-binding>
          </socket-binding-group>
      

      Since those are optional it would make sense to me to just write literal port number when property is empty

            spyrkob Bartosz Spyrko-Smietanko
            jbliznak@redhat.com Jan Blizňák
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: