[
https://issues.jboss.org/browse/AS7-2088?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2088:
----------------------------------------
I wouldn't use the word "inconsistent" here, since it's the format for
complex *values*.
But, honestly, I do agree the current format is not a user-friendly one and it has to be
improved.
The DMR format was the first natural choice, since at the end it's still gonna be a
DMR ModelNode. And, perhaps, it will still make sense to support this format even if we
come up with a friendlier CLI-specific format.
I'm gonna think more about this one and send an email to the dev list to discuss.
CLI usability: Parse compound operation parameters
--------------------------------------------------
Key: AS7-2088
URL:
https://issues.jboss.org/browse/AS7-2088
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
Currently, CLI does not parse compound operation parameters and relies on
ModelNode.fromString() method.
This means that an user have to use "key" => "value" notation to
denote compound parameters. This is inconsistent with the rest of CLI using
key="value" notation.
As an example, to add https connector one needs to use:
/subsystem=web/connector=https:add(socket-binding=https, scheme=https,
protocol="HTTP/1.1", enabled=true, ssl={ "certificate-key-file"
=>"/tmp/test.key"}))
command instead of more straightforward:
/subsystem=web/connector=https:add(socket-binding=https, scheme=https,
protocol="HTTP/1.1", enabled=true,
ssl={certificate-key-file="/tmp/test.key"}))
This is never documented.
Also any exceptions thrown by ModelNode.fromString() are discarded. I think they should
be reported back to the user. (DefaultCallbackHandler lines 448-453)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira