[jboss-jira] [JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

James Perkins (Jira) issues at jboss.org
Thu Aug 1 19:02:00 EDT 2019


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

James Perkins updated LOGMGR-259:
---------------------------------
    Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/272, https://github.com/jboss-logging/jboss-logmanager/pull/273, https://github.com/jboss-logging/jboss-logmanager/pull/274, https://github.com/jboss-logging/jboss-logmanager/pull/275, https://github.com/jboss-logging/jboss-logmanager/pull/276


> Named filters throw an IllegalArgumentException if they are embedded in an expression
> -------------------------------------------------------------------------------------
>
>                 Key: LOGMGR-259
>                 URL: https://issues.jboss.org/browse/LOGMGR-259
>             Project: JBoss Log Manager
>          Issue Type: Bug
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Major
>
> A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression.
> The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter.
> {code}
> logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test");
> logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)");
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list