On Aug 16, 2013, at 4:55 PM, Gary Gregory garydgreg...@gmail.com wrote:
On Fri, Aug 16, 2013 at 7:54 PM, Gary Gregory garydgreg...@gmail.comwrote:
On Fri, Aug 16, 2013 at 6:21 PM, David Nault david.na...@criticalpath.net
wrote:
Hi All,
We're using Log4j in a webapp and are looking at
I've had experiences where the ClassLoader used in the ServletContextListener
isn't the same as the ClassLoader the application uses. If that is the case
then the behavior you are seeing will occur. Unfortunately, this seems to vary
from one container to another.
Ralph
On Aug 19, 2013, at
On Fri, Aug 16, 2013 at 6:21 PM, David Nault
david.na...@criticalpath.netwrote:
Hi All,
We're using Log4j in a webapp and are looking at migrating to Log4j 2.
We'd like to continue writing our log files to a location under the
webapp's context root -- that is, under the directory returned
On Fri, Aug 16, 2013 at 7:54 PM, Gary Gregory garydgreg...@gmail.comwrote:
On Fri, Aug 16, 2013 at 6:21 PM, David Nault david.na...@criticalpath.net
wrote:
Hi All,
We're using Log4j in a webapp and are looking at migrating to Log4j 2.
We'd like to continue writing our log files to a
The BaseConfiguration has an initial set of Lookups that are hardwired so that
some variable substitution is possible on the attributes on the Configuration
element. Until the packages attribute is handled custom lookups won't be found.
Your custom Lookups should work for other elements in the
