[ https://issues.jboss.org/browse/WFLY-1395?page=com.atlassian.jira.plugin.... ] Ondrej Zizka updated WFLY-1395: ------------------------------- Description: Most operations don't follow any "overwrite" concept. To emulate it, one needs to check for existence of a resource, conditionally delete it, and then create the new one. This is not easily applicable in a batch. Implementing overwrite for all actions would be tedious. But this could help: Another "standard" property (except for address and op-name) would be "onFail=ignore" or such, which would make the operation not fail if an exception occurs. A short CLI syntax could be a '?' at the end of operation's name: {code} /foo=bar/boo=baz:remove?() {code} This would allow mgmt API users to queue a removing operation without knowing if it exists; thus, effectively, doing an overwrite. was: Most operations don't follow any "overwrite" concept. To emulate it, one needs to check for existence of a resource, conditionally delete it, and then create the new one. This is not easily applicable in a batch. Implementing overwrite for all actions would be tedious. But this could help: Another "standard" property (except for address and op-name) would be "onFail=ignore" or such, which would make the operation not fail if an exception occurs. This would allow mgmt API users to queue a removing operation without knowing if it exists; thus, effectively, doing an overwrite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira