Giacomo Pati schrieb:
Now, with Spring I would suggest the following approach:
Cocoon uses an own application context which can be compared (by
simplifying) with a service manager. So we have an application context
for the core of Cocoon (again simplified). Now you can define a root
Spring
Ralph Goers wrote:
If that is the case then I'm -1 on this. We use our own logging framework
with Cocoon.
I knew this would happen :) Ok, anyway, I would like to get rid off
excalibur
logging and logkit. Which means, we only use the o.a.a.logging.Logger
abstraction which is passed to a component
Carsten Ziegeler wrote:
I knew this would happen :) Ok, anyway, I would like to get rid off
excalibur
logging and logkit. Which means, we only use the o.a.a.logging.Logger
abstraction which is passed to a component through LogEnabled. And we
configure a Log4J logger by default for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 15 Feb 2006, Carsten Ziegeler wrote:
Date: Wed, 15 Feb 2006 14:20:12 +0100
From: Carsten Ziegeler [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Logkit (I know, again) was [RT] Using Spring instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Feb 2006, Carsten Ziegeler wrote:
Once we use the Spring based container we can simplify the whole setup
process and clean up things like the CoreUtil and the Cocoon class.
While we are at discussing cleanups.
What about also getting
Giacomo Pati wrote:
On Mon, 13 Feb 2006, Carsten Ziegeler wrote:
Once we use the Spring based container we can simplify the whole setup
process and clean up things like the CoreUtil and the Cocoon class.
While we are at discussing cleanups.
What about also getting rid of logkit and use
Le 13 févr. 06, à 14:50, Carsten Ziegeler a écrit :
Giacomo Pati wrote:
...What about also getting rid of logkit and use what we already have
in
our dependency lists (log4J, commons-logging, ...)?
Yes, please :) I would suggest log4j as commons-logging has problems
with classloading (afair)
Bertrand Delacretaz wrote:
Le 13 févr. 06, à 14:50, Carsten Ziegeler a écrit :
Giacomo Pati wrote:
...What about also getting rid of logkit and use what we already have in
our dependency lists (log4J, commons-logging, ...)?
Yes, please :) I would suggest log4j as commons-logging has
Upayavira wrote:
Bertrand Delacretaz wrote:
Le 13 févr. 06, à 14:50, Carsten Ziegeler a écrit :
Giacomo Pati wrote:
...What about also getting rid of logkit and use what we already have in
our dependency lists (log4J, commons-logging, ...)?
Yes, please :) I would suggest log4j as
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Feb 2006, Carsten Ziegeler wrote:
Once we use the Spring based container we can simplify the whole setup
process and clean up things like the CoreUtil and the Cocoon class.
While we are at discussing cleanups.
Carsten Ziegeler wrote:
...
Yes, please :) I would suggest log4j as commons-logging has problems
with classloading (afair) and noone is using jdk14 logging.
Nowadays there's also slf4j (www.slf4j.org). Like commons-logging it's a
facade for other logging frameworks but it doesn't suffer
Niklas Therning wrote:
Carsten Ziegeler wrote:
...
Yes, please :) I would suggest log4j as commons-logging has problems
with classloading (afair) and noone is using jdk14 logging.
Nowadays there's also slf4j (www.slf4j.org). Like commons-logging it's a
facade for other logging
Niklas Therning wrote:
Carsten Ziegeler wrote:
Yes, please :) I would suggest log4j as commons-logging has problems
with classloading (afair) and noone is using jdk14 logging.
Nowadays there's also slf4j (www.slf4j.org). Like commons-logging it's
a facade for other logging frameworks but it
Giacomo Pati wrote:
While we are at discussing cleanups.
What about also getting rid of logkit and use what we already have in
our dependency lists (log4J, commons-logging, ...)?
I think we definitively need to get a smaller footprint and also get
committed to fewer alternatives (of which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Feb 2006, Berin Loritsch wrote:
Date: Mon, 13 Feb 2006 09:58:06 -0500
From: Berin Loritsch [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Logkit (I know, again) was [RT] Using Spring instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Feb 2006, Ralph Goers wrote:
Date: Mon, 13 Feb 2006 07:07:58 -0800
From: Ralph Goers [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org, [EMAIL PROTECTED]
To: dev@cocoon.apache.org
Subject: Re: Logkit (I know, again) was [RT] Using Spring
Giacomo Pati wrote:
If the logger abstraction you mentioned is the Avalon LogEnabled one
than yes, we will still have to support that for backward compatability.
Of course we will support LogEnabled - with the only difference that you
always get a wrapper around a Log4J (or whatever we
Berin Loritsch wrote:
Niklas Therning wrote:
Carsten Ziegeler wrote:
Yes, please :) I would suggest log4j as commons-logging has problems
with classloading (afair) and noone is using jdk14 logging.
Nowadays there's also slf4j (www.slf4j.org). Like commons-logging it's
a facade for other
Ralph Goers wrote:
Carsten Ziegeler said:
Giacomo Pati wrote:
If the logger abstraction you mentioned is the Avalon LogEnabled one
than yes, we will still have to support that for backward compatability.
Of course we will support LogEnabled - with the only difference that you
always get a
Carsten Ziegeler said:
Ralph Goers wrote:
Carsten Ziegeler said:
What do you mean by always? I thought that we switched the default
from
logkit to log4j a while ago? What more is needed?
This switch never happened - the idea behind this is to remove the
support for other logging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Feb 2006, Ralph Goers wrote:
Date: Mon, 13 Feb 2006 13:16:37 -0800 (PST)
From: Ralph Goers [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Logkit (I know, again) was [RT] Using Spring instead
Giacomo Pati wrote:
-
Can you explain how you use your own under Cocoon? Separate LogEnabled
impls? CommonsLogging?
I implement org.apache.avalon.excalibur.logging.LoggerManager and
org.apache.avalon.excalibur.logging.Logger. These then interface with
my logging framework.
Ralph
On 14.02.2006, at 00:50, Carsten Ziegeler wrote:
Giacomo Pati wrote:
On Mon, 13 Feb 2006, Carsten Ziegeler wrote:
Once we use the Spring based container we can simplify the whole
setup
process and clean up things like the CoreUtil and the Cocoon class.
While we are at discussing
23 matches
Mail list logo
