[jboss-jira] [JBoss JIRA] (AS7-6713) CLI: "pattern" and "replacement" should be required when creating logging filter

[Chao Wang (JIRA)]

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

Chao Wang updated AS7-6713:
---------------------------

    Attachment: AS7-6713.patch


patch to check "pattern" and "replacement" values can't be undefined from LoggingWriteAttributeHandler.validateUpdatedModel()
                
> CLI: "pattern" and "replacement" should be required when creating logging filter
> --------------------------------------------------------------------------------
>
>                 Key: AS7-6713
>                 URL: https://issues.jboss.org/browse/AS7-6713
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>         Attachments: AS7-6713.patch
>
>
> It's able to set filter attribute without "pattern" and "replacement" although they are not nillable.
> calling:
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value={replace => {"replace-all" => true}})
> will create useless filter:
> "filter" => {"replace" => {
>     "replace-all" => true,
>     "pattern" => "undefined",
>     "replacement" => "undefined"
> }}
> "filter-spec" => "substituteAll(\"undefined\",\"undefined\")"
> only "replace-all" is actually required now:
> [standalone at localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:update-properties(filter={replace => {"pattern" => "JBAS","replacement" => "SABJ"}})
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014749: Operation handler failed: null",
>     "rolled-back" => true
> }

--
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