logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-776) Using custom path and file name for log4j2 config file in EJB3
Date Sat, 16 Aug 2014 11:56:18 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099611#comment-14099611
] 

A B commented on LOG4J2-776:
----------------------------

Matt Slacker mentioned that I should open a feature request for EJB3 as currently that functionality
is unavailable.  So changing this to New Feature

> 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
>            Priority: Minor
>
> 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.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message