Kabir Khan created WFCORE-1034: ---------------------------------- Summary: 2 step domain operations do not resolve aliases properly Key: WFCORE-1034 URL: https://issues.jboss.org/browse/WFCORE-1034 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.0.0.CR6 Reporter: Kabir Khan Assignee: Kabir Khan Priority: Critical Fix For: 2.0.0.CR7 For WFLY-5290, WFCORE-1022 was done to provide more context, however we still have some problems when doing: {code} /profile=full-ha/subsystem=jgroups/stack=tcp/transport=TRANSPORT/thread-pool=default:write-attribute(name=keepalive-time,value=100) {code} This is an alias which should resolve to {code} /profile=full-ha/subsystem=jgroups/stack=tcp/transport=TCP/thread-pool=default:write-attribute(name=keepalive-time,value=100) {code} The equivalent works fine in a standalone. Debugging using CLI commands, the initial read-operation-description ends up in PrepareStepHandler.executeDirectOperation() which does the right thing. However the write-attribute call ends up in {code} OperationCoordinatorStepHandler.execute() -> OperationSlaveStepHandler.addSteps() -> HostControllerExecutionSupport returns a domainOp -> OperationSlaveStepHandler.addBasicStep() {code} and OperationSlaveStepHandler.addBasicStep() resolves the OperationEntry differently from the standard/standalone prepare step handler, and from how PrepareStepHandler.executeDirectOperation() resolves it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)