[
https://issues.apache.org/jira/browse/LOG4J2-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962606#comment-13962606
]
Ralph Goers commented on LOG4J2-598:
------------------------------------
I would have to look at the plugins we have created. We should do the normal
strategy of aiming to cover the top 80% of what is happening in a typical
plugin factory as far as parameter validation goes. I could envision that
things like min and max values, or a list of valid values might be there but I
would take these things one at a time. Starting with just doing the data
conversion from Strings in XML or JSON to the correct data type goes a long way
towards simplification.
> Support more data types in plugin attributes
> --------------------------------------------
>
> Key: LOG4J2-598
> URL: https://issues.apache.org/jira/browse/LOG4J2-598
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-rc1
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Priority: Minor
> Labels: annotations, plugins
>
> Currently, annotating plugin factory method parameters with
> {{@PluginAttribute}} only supports String types, but we use a lot of plugin
> attributes that could be automatically converted to primitive types. Now I'm
> not suggesting something as advanced as how Camel handles parameter injection
> (which does automatic non-trivial type conversion), but it would be great to
> support booleans, ints, longs, etc., to simplify quite a bit of extraneous
> string parsing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
