[
https://issues.apache.org/jira/browse/LOG4J2-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532950#comment-17532950
]
Matt Sicker commented on LOG4J2-3497:
-------------------------------------
PluginRegistry keeps a cache of scanned plugins. PluginManager gives you a way
to look up plugins by category. Different plugin categories are instantiated
differently (in 2.x), with the "Core" category plugins using the PluginBuilder
class (and related visitors) along with constraint validators supported
directly in PluginBuilder. The key point of confusion, I think, is that
PluginBuilder is only used for Core category plugins. In 3.0, I've overhauled
every category of plugin to support generic dependency injection (which even
includes things such as the node visitors, constraint validators, and
essentially anything that can be created by Injector; the main limitations
there would revolve around startup ordering in that it's difficult to depend on
something that depends on the thing you're already making unless you introduce
a Supplier<T> indirection). This also means that constraint validators are
supported on all plugins in 3.0.
If you're looking to support constraints in more plugin categories in 2.x,
those would need to be done piecemeal.
> ConstraintValidator's are not employed by PluginManager
> -------------------------------------------------------
>
> Key: LOG4J2-3497
> URL: https://issues.apache.org/jira/browse/LOG4J2-3497
> Project: Log4j 2
> Issue Type: Bug
> Components: Plugins
> Reporter: Volkan Yazici
> Assignee: Matt Sicker
> Priority: Major
> Fix For: 2.18.0
>
>
> {{ConstraintValidator}}'s are not taken into account when plugins are
> collected via {{PluginManager}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
