I am 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@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 }
Need an upstream JIRA.
Chao Wang <chaowan> made a comment on jira AS7-6713 patch to check "pattern" and "replacement" values can't be undefined from LoggingWriteAttributeHandler.validateUpdatedModel()
James Perkins <jperkins> made a comment on jira AS7-6713 Writing a fix for this and testing various other filters I think I opened Pandora's box :-). I'll suggest for a workaround use the {{filter-spec}} expressions instead. I'll also note, I should probably document those.
Chao Wang <chaowan> made a comment on jira AS7-6713 wrt filter-spec expression, I tried to configure something similar, but unsuccessfully as described in https://community.jboss.org/thread/222386
Behaviour described in description is fixed. There is new info message that filter attribute is deprecated and thus should not be used. Closing Pandora's box :). Verified with EAP 6.1 ER4
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html