Hi All
Another way to bundle your log4j.properties is to include it in the
framework /application jar and then use the log4j.conifguration system
property if you need to change the defaults in teh deployment environment.
That way there is no log4j configuration code in the application/framework
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString();
then I have:
System.out.println(Log4j file (from .woa): +
never mind.
On Aug 15, 2007, at 10:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null,
On Aug 15, 2007, at 8:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString();
Try
URL
Don't leave us hanging ;-) What was the fix?
On Aug 15, 2007, at 12:04 PM, James Cicenia wrote:
never mind.
On Aug 15, 2007, at 10:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
LOL !
I instead used URL, just as Chuck was probably writing his reply.
HOWEVER!!!
for some reason if I just put a static string in the argument it
worked?!
i.e.
PropertyConfigurator.configure(/blah/blah/blah/log4j.properties)
That I don't understand.
Best to have it here in the archives.
On Aug 15, 2007, at 9:25 AM, James Cicenia wrote:
LOL !
I instead used URL, just as Chuck was probably writing his reply.
HOWEVER!!!
for some reason if I just put a static string in the argument it
worked?!
i.e.
PropertyConfigurator.configure(/blah/blah/blah/log4j.properties)
That I
