Cause:
The handler for the 'add' management operation for the remote-outbound-connection resources did not properly account for the possibility of an expression being the value of the username attribute.
Consequence:
If an expression is used as the value for the 'username' attribute, the unresolved string will be used as the user name, rather than the resolved value.
Fix:
The handler now uses standard attribute handling for this attribute, ensuring expression support.
Result:
If an expression is used for the 'username' attribute, the resolved value will now be used.
Description of problem:
Expressions not resolved for username attribute in remote-outbound-connection in remoting subsystem
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
...
<remote-outbound-connection name="remote-ejb-connection1" outbound-socket-binding-ref="remote-ejb-1" username="${remote-ejb-user}" security-realm="ejb-security-realm">
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
The username is not resolved to a the property that is being set.
Expected results:
The username is resolved to the property being set.
Additional info:
This issue is already resolved in WFLY core.
Description of problem: Expressions not resolved for username attribute in remote-outbound-connection in remoting subsystem <subsystem xmlns="urn:jboss:domain:remoting:1.1"> ... <remote-outbound-connection name="remote-ejb-connection1" outbound-socket-binding-ref="remote-ejb-1" username="${remote-ejb-user}" security-realm="ejb-security-realm"> Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: The username is not resolved to a the property that is being set. Expected results: The username is resolved to the property being set. Additional info: This issue is already resolved in WFLY core.