[
https://issues.redhat.com/browse/WFCORE-5253?page=com.atlassian.jira.plug...
]
Brian Stansberry updated WFCORE-5253:
-------------------------------------
Description:
Some of the OperationStepHandler impls in the remoting subsystem are reading the data they
provide to runtime services from the current operation instead of reading from the current
configuration model.
As part of cleaning this up I'll do some conversion of reads of the current address
from extracting it from the 'operation' model node to the modern idiom of using
OperationContext.getCurrentAddress[Value]().
I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places
where not-incorrect but non-standard idioms are used.
was:
Some of the OperationStepHandler impls in the remoting subsystem are reading the data the
provide to runtime services from the current operation instead of reading from the current
configuration model.
As part of cleaning this up I'll do some conversion of reads of the current address
from extracting it from the 'operation' model node to the modern idiom of using
OperationContext.getCurrentAddress[Value]().
I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places
where not-incorrect but non-standard idioms are used.
Incorrect use of 'operation' instead of Resource in the
remoting subsystem
--------------------------------------------------------------------------
Key: WFCORE-5253
URL:
https://issues.redhat.com/browse/WFCORE-5253
Project: WildFly Core
Issue Type: Bug
Components: Remoting
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
Some of the OperationStepHandler impls in the remoting subsystem are reading the data
they provide to runtime services from the current operation instead of reading from the
current configuration model.
As part of cleaning this up I'll do some conversion of reads of the current address
from extracting it from the 'operation' model node to the modern idiom of using
OperationContext.getCurrentAddress[Value]().
I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places
where not-incorrect but non-standard idioms are used.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)