Yeah, that should be enough. Verify that Log4J is actually used, and
that that properties file (log4j.properties) is actually loaded by
Log4J. Additionally, you can have this in your classpath:
commons-logging.properties with:
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger,
though I think that's not a necessity.
Eelco
On 9/3/06, David Leangen <[EMAIL PROTECTED]> wrote:
>
> Hello!
>
> Could somebody please remind me how the logging factory works?
>
> I'm trying to get XFire working in OSGi, and I need to wire up the
> logging to figure out what's going on.
>
> XFire does this:
>
> private final static Log logger =
> LogFactory.getLog(XFireServlet.class);
>
>
> Should that not be enough?
>
> I put a log4j.properties file on my classpath. These are the contents:
>
> log4j.logger=DEBUG, Console
>
> log4j.appender.Console=org.apache.log4j.ConsoleAppender
> log4j.appender.Console.layout=org.apache.log4j.PatternLayout
> log4j.appender.Console.layout.ConversionPattern=%d %-5p [%t] %c{2} - %m%
> n
>
>
>
> Any suggestions would be most appreciated!
>
>
>
>
> _______________________________________________
> general mailing list
> [EMAIL PROTECTED]
> http://lists.ops4j.org/mailman/listinfo/general
>
_______________________________________________
general mailing list
[EMAIL PROTECTED]
http://lists.ops4j.org/mailman/listinfo/general
