Exception logging

mock1010 · **Joined:** Tue Jun 08, 2004 8:24 am **Posts:** 57

Would it be possible in future releases of Hibernate to remove the automatic exception logging?

Example:

Code:

package org.hibernate;

import org.apache.commons.logging.LogFactory;

public class LazyInitializationException extends HibernateException {

   public LazyInitializationException(String msg) {
      super(msg);
      LogFactory.getLog(LazyInitializationException.class).error(msg, this);
   }

}

I can quite easily catch the exception in my own code and print out a stack trace, or not as my needs may dictate. No need to force it to print and make me put a bunch of logging filters in my log4j settings file.
[/code]

tenwit · **Joined:** Thu Dec 23, 2004 9:08 pm **Posts:** 2008

With luck, no. This is a good log. Adding "log4j.logger.org.hibernate=FATAL" to your log4j.properties won't hurt you too much, and it means the rest of us don't have to change our existing log4j.properties files.

mock1010 · **Joined:** Tue Jun 08, 2004 8:24 am **Posts:** 57

I'm not trying to turn off all Hibernate logs. The error logs are a good thing.

What I don't want is to have error messages spit out for an exception that I'm catching and handling (in this case, a bean copier that uses reflection, and ignores any properties not lazy-loaded by the time the session closes).

If the exception bubbles to the top, it will be reported by either the JVM or your application framework.
Putting an error log message in the constructor of an exception is a bad thing.