[jboss-jira] [JBoss JIRA] (WFLY-1508) Transformer builders should not check for rejected operation attributes for the 'remove' operation

[Kabir Khan (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kabir Khan updated WFLY-1508:
-----------------------------

    Description: 
I came across this while working on WFLY-456 (audit logging) that PR will test for this

The problem is the audit log transformers for jmx are set up to reject if the 'enabled' attribute is undefined.
When issuing a 'remove' it then looks in the operation for the 'enabled' attribute which fails since the operation does not contain that attribute, it is simply:
{code}
{
    "operation" => "remove",
    "address" => [
        ("subsystem" => "jmx"),
        ("configuration" => "audit-log")
    ]
}
{code}
The same is true for 'read-attribute'

  was:
I came across this while working on WFLY-456 (audit logging). I will submit this as part of that PR.

The problem is the audit log transformers for jmx are set up to reject if the 'enabled' attribute is undefined.
When issuing a 'remove' it then looks in the operation for the 'enabled' attribute which fails since the operation does not contain that attribute, it is simply:
{code}
{
    "operation" => "remove",
    "address" => [
        ("subsystem" => "jmx"),
        ("configuration" => "audit-log")
    ]
}
{code}
The same is true for 'read-attribute'


    
> Transformer builders should not check for rejected operation attributes for the 'remove' operation
> --------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1508
>                 URL: https://issues.jboss.org/browse/WFLY-1508
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>             Fix For: 8.0.0.Alpha3
>
>
> I came across this while working on WFLY-456 (audit logging) that PR will test for this
> The problem is the audit log transformers for jmx are set up to reject if the 'enabled' attribute is undefined.
> When issuing a 'remove' it then looks in the operation for the 'enabled' attribute which fails since the operation does not contain that attribute, it is simply:
> {code}
> {
>     "operation" => "remove",
>     "address" => [
>         ("subsystem" => "jmx"),
>         ("configuration" => "audit-log")
>     ]
> }
> {code}
> The same is true for 'read-attribute'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira