[
https://issues.apache.org/jira/browse/LOG4J2-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-846:
-------------------------------
Fix Version/s: (was: 2.3)
> Combine Log4jWebInitializerImpl into a LoggerContext/LifeCycle wrapper class
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-846
> URL: https://issues.apache.org/jira/browse/LOG4J2-846
> Project: Log4j 2
> Issue Type: Task
> Components: Web/Servlet
> Affects Versions: 2.1
> Reporter: Matt Sicker
> Assignee: Matt Sicker
>
> This idea is somewhat inspired by Spring's
> WebApplicationContext/ApplicationContext separation of concerns. Basically,
> make a WebLoggerContext interface that extends the API LoggerContext
> interface, have it also extend LifeCycle, and combine the functionality in
> Log4jWebInitializerImpl into this class instead.
> The reasoning for this change is to work on a way to allow the user to
> perform additional configuration and such in a web container similar to
> Spring's
> [WebApplicationInitializer|http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/web/WebApplicationInitializer.html]
> interface. This would also provide another stepping stone to programmatic
> configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
