You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2016/09/09 14:00:32 UTC
[jira] [Closed] (LOG4J2-1565) PluginManager should be able to load
plugins via SPI
[ https://issues.apache.org/jira/browse/LOG4J2-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker closed LOG4J2-1565.
-------------------------------
Resolution: Information Provided
Closing as per request, but if this feature is still requested in the future, the issue can be reopened.
> PluginManager should be able to load plugins via SPI
> ----------------------------------------------------
>
> Key: LOG4J2-1565
> URL: https://issues.apache.org/jira/browse/LOG4J2-1565
> Project: Log4j 2
> Issue Type: Wish
> Components: Plugins
> Affects Versions: 2.6.2
> Reporter: Philip Helger
>
> I want to setup a custom configuration using a special factory class (based on https://logging.apache.org/log4j/2.x/manual/customconfig.html)
> As this will run in an Application server I don't have access to the system properties or to the main to call {{ConfigurationFactory.setConfigurationFactory}}
> Therefore I suggest to add an SPI loading mechanism for ConfigurationFactory as well. See https://docs.oracle.com/javase/tutorial/ext/basics/spi.html for details on SPI.
> Do you think this could work, or would this be a problem, if Tomcat itself is configured to use log4j? Maybe it can be done upon Servlet initialization as done in the log4j2-web project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org