[
https://issues.apache.org/jira/browse/TOMEE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reopened TOMEE-1214:
----------------------------------
The problem basically remains the same even after your fix.
The point is that it doesn't even enter the new path as it finds the
logging.properties (which are intended for jul only by default it seems) and
skips all the later processing.
I'm not sure why we read logging.properties at all if log4j is configured...
> tomee should pick up conf/log4j.xml
> -----------------------------------
>
> Key: TOMEE-1214
> URL: https://issues.apache.org/jira/browse/TOMEE-1214
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 1.6.0.1
> Reporter: Mark Struberg
> Assignee: Romain Manni-Bucau
> Fix For: 1.7.0
>
>
> If a user sets -Dopenejb.log.factory=log4j then we currently only look for
> logging.properties in our /conf folder.
> We should also pick up conf/log4j.xml that way _after_
> conf/logging.properties, but _before_ the internal default config.
> If there is a conf/logging.properties then we will of course _not_ check for
> log4j.xml...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
