[
https://issues.apache.org/jira/browse/LOG4J2-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343212#comment-14343212
]
Ralph Goers commented on LOG4J2-776:
------------------------------------
Log4j-api was separated so that applications would know what was guaranteed to
remain compatible. Once you start talking about configuration, dynamically
creating appenders or other things like that you are working against things
that are part of the log4j implementation, so they aren't guaranteed to remain
100% compatible. That said, there are many parts of the implementation that are
not likely to change in a way that will cause you problems. These would include
relying on the methods in the code above. In short, if it is documented on the
web site it isn't likely it will change.
> Using custom path and file name for log4j2 config file in EJB3
> --------------------------------------------------------------
>
> Key: LOG4J2-776
> URL: https://issues.apache.org/jira/browse/LOG4J2-776
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
> Affects Versions: 2.0.1
> Environment: Windows 7, Websphere 8.5, EJB 3.1
> Reporter: A B
>
> When using log4j ( 1.x ) with EJB, you could define / set / load the custom
> log4j configuration file and define the location of the configuration file by
> using the @Startup bean with @PostConstruct and then call
> PropertyConfigurator.configure(log4jProp); to load the configuration where
> log4jProp would be the location AND filename for the config file
> Since the above method is not valid in log4j2, what method / mechanism should
> be used to load a specific configuration in an EJB3 module?
> Also, how can I use an environment / system variable to define the
> configuration file name ( as done in Jira item 747 for log4j for a servlet )?
> Thank you,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
