[
https://issues.jboss.org/browse/WFCORE-2850?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-2850:
-------------------------------------
I'm deferring this t o4. I thought I'd updated the places in full that needed
updating to account for this, but I must have dreamed that. Looking at all the uses of
AbstractRuntimeOnlyHandler in full, too many need update to take it on at this stage of
the release cycle and the number of them make me question whether by default disabling the
op in a runtime-only server is the right thing to do.
AbstractRuntimeOnlyHandler should not add its step on a profile=*
resource
---------------------------------------------------------------------------
Key: WFCORE-2850
URL:
https://issues.jboss.org/browse/WFCORE-2850
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The child resources of /profile=* do not have a runtime behind them, so
AbstractRuntimeOnlyStepHandler should not add its Stage.RUNTIME step if the target
resources is in that tree.
This will make it possible to use this class if as part of WFCORE-389 we lift the
(currently unenforced) restriction on adding runtime-only ops to profile resources in
order to have the DC roll them out to relevant servers. It's particular important in
the context of the related WFCORE-2815, which would result in the current
AbstractRuntimeOnlyStepHandler impl failing if used on a profile resource, since the step
it adds would be rejected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)