[
https://issues.jboss.org/browse/JBAS-9140?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-9140:
----------------------------------------
If you can figure out what changed elsewhere, that would be better than quoting. I'm
concerned it's a jboss-dmr bug.
But if you can't figure it out fairly quickly or it's not a bug, yes, recognizing
and quoting should be fine. That should result in a ModelNode of ModelType.STRING, and if
you call .asBoolean() on that you get back a proper answer. Only negative is if some
OperationHandler directly stores the operation value, the internal model will have, e.g.
"fixed-port" => "true"
instead of
"fixed-port" => true
Not a big deal, just not tidy.
Can you point me where in the CLI this ModelNode gets created? I poked a bit, but
didn't see it. I'm curious to know regardless of how we fix this. :)
Incorrect value for boolean parameter
-------------------------------------
Key: JBAS-9140
URL:
https://issues.jboss.org/browse/JBAS-9140
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: CLI
Reporter: Brian Stansberry
Assignee: Alexey Loubyansky
With the latest from master, this operation:
/socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=fixed-port,value=true)
results in this operation on the server (incorrect value):
{
"operation" => "write-attribute",
"name" => "fixed-port",
"value" => false,
"address" => [
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "http")
]
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira