[
https://issues.jboss.org/browse/WFLY-2946?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-2946:
----------------------------------------
There might be other examples besides this one, but I can certainly imagine a case where a
single 'add' would produce a resource tree instead of just a single resource. And
the CLI wouldn't be able to know that would happen.
For example, a resource with child resources for various properties might take an optional
'properties' param in its add handler and if present just add all the children.
Improve 'cd' behavior in batch mode
-----------------------------------
Key: WFLY-2946
URL:
https://issues.jboss.org/browse/WFLY-2946
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: CLI
Affects Versions: 8.0.0.Final
Reporter: Brian Stansberry
Assignee: Alexey Loubyansky
See discussion at
https://community.jboss.org/message/858108#858108 for background.
The problem is the 'cd' behavior discussed in my comment. A 'cd' in batch
mode seems to have triggered the CLI validating the location (or some other op against the
address), which fails since the previous batch step that created the location hasn't
executed.
Would it be better to simply accept the address in batch mode, or somehow be a bit
smarter?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)