[ https://issues.redhat.com/browse/WFCORE-2687?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-2687: ------------------------------------- Description: Remove the need to pass the 'operation' ModelNode to a method for it to be able to learn about the currently effective operation. OperationContext already exposes getCurrentAddress(). Add getCurrentOperationName() and getCurrentOperationParameter(String name). The latter returns null if !operation.has(name) otherwise it returns whatever the node was. Or perhaps return undefined with an overloaded variant with a boolean param that lets the caller turn on getting null. The getCurrentOperationParameter should reject 'operation', 'address', 'operation-headers' etc as legal param names; only expose true parameters. EDIT: I removed 'name' from the list of illegal param names. It's not a special key in an operation model node. I added 'operation', which is a special key. I suspect when I wrote this I confused myself because the value of 'operation' key is the name of the operation. was: Remove the need to pass the 'operation' ModelNode to a method for it to be able to learn about the currently effective operation. OperationContext already exposes getCurrentAddress(). Add getCurrentOperationName() and getCurrentOperationParameter(String name). The latter returns null if !operation.has(name) otherwise it returns whatever the node was. Or perhaps return undefined with an overloaded variant with a boolean param that lets the caller turn on getting null. The getCurrentOperationParameter should reject 'address', 'operation-headers' etc as legal param names; only expose true parameters. EDIT: I removed 'name' from the list of illegal param names. It's not a special key in an operation model node. -- This message was sent by Atlassian Jira (v7.13.8#713008)