Description of problem:
No outbound socket details are visible if any of the ports uses an expression

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Change 

        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="localhost" port="25"/>
        </outbound-socket-binding>

To **replacing port="25" with port="${app.smtp:25}" i.e an expression 

        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="localhost" port="${app.smtp:25}"/>
        </outbound-socket-binding>

2. View the the "outbound remote" tab in http://localhost:9990/console/App.html#socket-bindings

3. The mail-smtp outbound socket is no longer is visible in the console.

4. Snippet from trace logs

------

16:2516:25:44,607 TRACE [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 2) Executing "read-children-resources" [("socket-binding-group" => "standard-sockets")]
16:25:44,609 TRACE [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 3) Executing "read-children-resources" [("socket-binding-group" => "standard-sockets")]
:44,617 TRACE [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 3) Prepared response is {
    "outcome" => undefined,
    "result" => {"mail-smtp" => {
        "fixed-source-port" => false,
        "host" => "localhost",
        "port" => expression "${app.smtp:25}",
        "source-interface" => undefined,
        "source-port" => undefined
    }}
}
------

Actual results:
No outbound socket config is visible if *any* of them uses an expression for its ports 


Expected results:
Outbound socket config should be visible via the admin console if any of the attributes use expressions  

Additional info:

You can test adding one outbound socket which uses no expressions and then another one which uses an expression for its ports. Same results i.e nothing rendered in the admin console.