[
https://issues.apache.org/jira/browse/LOG4J2-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342834#comment-14342834
]
Gary Gregory commented on LOG4J2-776:
-------------------------------------
I think Remko already answered your question ;-) The Core module is not the
public API, but it is important for non-trivial usage. I think the config APIs
will likely remain the stable unless we need to fix something or implement a
new feature. For now, the only module that is set in stone within the 2.x
branch is the log4j-api module and 1.2 compatibility module.
> 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]
