1.4-dev: Exception depending on log4j level (debug versus warn ...)

Michael Wechner wrote:
> Hi
> 
> I have discovered something very unusual.
> 
> If I use the "debug" level for log4j, then
I receive the following 
> exception within the blog publication:
> 
> No resource type defined for document
[blog:authoring:/feeds/all/index:en]!
> 
> on the browser screen.
> 
> BUT if use "warn" level for log4j, then
everything is fine, whereas in 
> the log file there is still
> the same error.
> 
> Any idea what might be causing this?

AbstractUsecase.java:224


     if (getLogger().isDebugEnabled()) {
         throw new UsecaseException(e);
     }


If in DEBUG mode, it throws the exception straightaway so
you
don't have to search the log files. I find this very
useful.

-- Andreas



-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
andreas.hartmannwyona.com                     andreasapache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org