ible problems when using log4j, or other
loggers, directly in applications:
http://jetty.mortbay.org/jetty5/tut/logging.html
Jonathan
-Original Message-
From: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 05, 2008 4:06 PM
To: Tapestry users
Subject: Re: T5: How d
lems when using log4j, or other
loggers, directly in applications:
http://jetty.mortbay.org/jetty5/tut/logging.html
Jonathan
> -Original Message-
> From: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 4:06 PM
> To: Tapestry users
> Subje
Hi Jonathan,
I know about slf4j, I'm just using log4j as my framework of choice - for
now.
Regarding app server... I'm actually just running this through Jetty
(using the Maven plugin) right now, but will be deploying to Tomcat in
production - it's not a big application.
-Filip
Jonathan B
Actually, the default is still pretty much log4j, but we're using
slf4j instead of commons-logging as the wrapper around log4j. It's
easy to override to a different logging package as well.
On Feb 5, 2008 11:44 AM, Jonathan Barker <[EMAIL PROTECTED]> wrote:
> Filip,
>
> Recent versions of T5 have
Filip,
Recent versions of T5 have used slf4j, not log4j. Having said that, the
underlying logger is often log4j.
What app server?
JBoss, for example, has all logging configured through a log4j.xml file in
the server conf directory.
Jonathan
> -Original Message-
> From: Filip S. Ada
Logging is based on the class name of the module that defined the
service, then the service id, i.e.
log4j.category.org.example.myapp.services.AppModule.MyService=info
On Feb 5, 2008 11:24 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm having trouble configuring logging for my ser
