[jboss-jira] [JBoss JIRA] (WFCORE-4042) "filter-spec" attribute of socket-handler contains non existent "filter" alternative

[Claudio Miranda (JIRA)]

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

Claudio Miranda updated WFCORE-4042:
------------------------------------
    Description: 
The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute
{code}
"filter-spec" => {
    "type" => STRING,
    "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))",
    "expressions-allowed" => true,
    "required" => false,
    "nillable" => true,
    "alternatives" => ["filter"],
    "min-length" => 1L,
    "max-length" => 2147483647L,
    "access-type" => "read-write",
    "storage" => "configuration",
    "restart-required" => "no-services"
},
{code}

I counted the following resources affected by the issue.
{code}
/logging-profile=*/async-handler=*
/logging-profile=*/console-handler=*
/logging-profile=*/custom-handler=*
/logging-profile=*/file-handler=*
/logging-profile=*/periodic-rotating-file-handler=*
/logging-profile=*/periodic-size-rotating-file-handler=*
/logging-profile=*/size-rotating-file-handler=*
/logging-profile=*/socket-handler=*
/logging-profile=*/root-logger=ROOT
/periodic-size-rotating-file-handler=*
/socket-handler=*
{code}

In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata.

  was:
The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute
{code}
"filter-spec" => {
    "type" => STRING,
    "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))",
    "expressions-allowed" => true,
    "required" => false,
    "nillable" => true,
    "alternatives" => ["filter"],
    "min-length" => 1L,
    "max-length" => 2147483647L,
    "access-type" => "read-write",
    "storage" => "configuration",
    "restart-required" => "no-services"
},
{code}

I counted the following resources affected by the issue.
{code}
/logging-profile=*/async-handler=*
/logging-profile=*/console-handler=*
/logging-profile=*/custom-handler=*
/logging-profile=*/file-handler=*
/logging-profile=*/periodic-rotating-file-handler=*
/logging-profile=*/periodic-size-rotating-file-handler=*
/logging-profile=*/size-rotating-file-handler=*
/logging-profile=*/socket-handler=*
/periodic-size-rotating-file-handler=*
/socket-handler=*
{code}

In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata.



> "filter-spec" attribute of socket-handler contains non existent "filter" alternative
> ------------------------------------------------------------------------------------
>
>                 Key: WFCORE-4042
>                 URL: https://issues.jboss.org/browse/WFCORE-4042
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Claudio Miranda
>            Assignee: James Perkins
>
> The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute
> {code}
> "filter-spec" => {
>     "type" => STRING,
>     "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))",
>     "expressions-allowed" => true,
>     "required" => false,
>     "nillable" => true,
>     "alternatives" => ["filter"],
>     "min-length" => 1L,
>     "max-length" => 2147483647L,
>     "access-type" => "read-write",
>     "storage" => "configuration",
>     "restart-required" => "no-services"
> },
> {code}
> I counted the following resources affected by the issue.
> {code}
> /logging-profile=*/async-handler=*
> /logging-profile=*/console-handler=*
> /logging-profile=*/custom-handler=*
> /logging-profile=*/file-handler=*
> /logging-profile=*/periodic-rotating-file-handler=*
> /logging-profile=*/periodic-size-rotating-file-handler=*
> /logging-profile=*/size-rotating-file-handler=*
> /logging-profile=*/socket-handler=*
> /logging-profile=*/root-logger=ROOT
> /periodic-size-rotating-file-handler=*
> /socket-handler=*
> {code}
> In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)