Details
-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.Final
Description
socket bindings return on read expression in the form {"EXPRESSION_VALUE":"${foo:123}"}
[standalone@localhost:9999 socket-binding=management-http] :read-attribute(name=port)
{
"outcome" => "success",
"result" => expression "${jboss.management.http.port:9990}"
}
First this is confusing, as the description describes the port as int:
[standalone@localhost:9999 socket-binding=http] :read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "Configuration information for a socket.",
"attributes" => {
"port" =>
,
I can still work around this in json-land by having the expression toString()'d and then remove the
{EXPRESSION_VALUE=..}part around it.
Now writing back an expression does not work:
[standalone@localhost:9999 socket-binding=management-http] :write-attribute(name=port,value=${jboss.management.http.port:19990})
{
"outcome" => "failed",
"failure-description" => "JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING",
"rolled-back" => true
}
Same applies to json-interface when I do a write-attribute call with {name="port",value="${...}"} as payload
Operation <CompositeOperation
> returned <"JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING","rolled-back":true},