You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Joerg Heinicke <jo...@gmx.de> on 2008/08/29 00:10:45 UTC
Re: svn commit: r689749 - /cocoon/whiteboard/corona/trunk/corona-sitemap/src/main/java/org/apache/cocoon/corona/sitemap/InvocationImpl.java
On 28.08.2008 09:47, reinhard@apache.org wrote:
> Author: reinhard
> Date: Thu Aug 28 00:47:42 2008
> New Revision: 689749
>
> URL: http://svn.apache.org/viewvc?rev=689749&view=rev
> Log:
> improve error reporting: print the full stacktrace when the loglevel is set to INFO or below. Otherwise only print the first 5 lines.
Shouldn't these kind of things be left to the logging implementation and
configuration?
Joerg
Re: svn commit: r689749 - /cocoon/whiteboard/corona/trunk/corona-sitemap/src/main/java/org/apache/cocoon/corona/sitemap/InvocationImpl.java
Posted by Joerg Heinicke <jo...@gmx.de>.
On 29.08.2008 07:45, Reinhard Pötz wrote:
>>> URL: http://svn.apache.org/viewvc?rev=689749&view=rev
>>> Log:
>>> improve error reporting: print the full stacktrace when the loglevel
>>> is set to INFO or below. Otherwise only print the first 5 lines.
>> Shouldn't these kind of things be left to the logging implementation and
>> configuration?
>
> If I knew how to do this ... Log4j isn't really well documented.
I don't know either. I just "felt" wrong. Somebody else might know how
to do it or implement his own formatter.
I saw you already removed it. Thanks :)
Joerg
Re: svn commit: r689749 - /cocoon/whiteboard/corona/trunk/corona-sitemap/src/main/java/org/apache/cocoon/corona/sitemap/InvocationImpl.java
Posted by Reinhard Pötz <re...@apache.org>.
Joerg Heinicke wrote:
> On 28.08.2008 09:47, reinhard@apache.org wrote:
>
>> Author: reinhard
>> Date: Thu Aug 28 00:47:42 2008
>> New Revision: 689749
>>
>> URL: http://svn.apache.org/viewvc?rev=689749&view=rev
>> Log:
>> improve error reporting: print the full stacktrace when the loglevel
>> is set to INFO or below. Otherwise only print the first 5 lines.
>
> Shouldn't these kind of things be left to the logging implementation and
> configuration?
If I knew how to do this ... Log4j isn't really well documented.
Any hints?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________