[jboss-jira] [JBoss JIRA] (WFCORE-545) Inconsistent stage for adding/updating/removing system properties

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050368#comment-13050368 ] 

RH Bugzilla Integration commented on WFCORE-545:
------------------------------------------------

Carlo de Wolf <cdewolf at redhat.com> changed the Status of [bug 1190918|https://bugzilla.redhat.com/show_bug.cgi?id=1190918] from ASSIGNED to CLOSED

> Inconsistent stage for adding/updating/removing system properties
> -----------------------------------------------------------------
>
>                 Key: WFCORE-545
>                 URL: https://issues.jboss.org/browse/WFCORE-545
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 1.0.0.Alpha18
>            Reporter: Brian Stansberry
>            Assignee: ehsavoie Hugonnet
>            Priority: Minor
>             Fix For: 1.0.0.Alpha19
>
>
> SystemPropertyAddHandler and SystemPropertyValueWriteAttributeHandler both update the VM property map during Stage.MODEL, while SystemPropertyRemoveHandler waits until Stage.RUNTIME.
> This can lead to unintuitive behavior in a composite op, e.g. if a user does a remove and then an add in a batch to change the value. The remove will actually update the runtime after the add, resulting in the prop being unset.
> The SystemPropertyAddHandler and SystemPropertyValueWriteAttributeHandler behavior is non-standard as they change non-model information in Stage.MODEL, but that was done deliberately (I forget exactly why.) So the fix should be to adapt SystemPropertyRemoveHandler.
> This is minor because the remove + add in a composite workflow is a harder-to-use alternative to using a single write-attribute op.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)