(I'm using hibernate-1.1)
I'm integrating a lot of different frameworks that all use log4j as their logging mechanism. In all of the other frameworks, WARN level messages are reserved for "pathological conditions". They indicate that something is seriously out of whack, but perhaps not seriously enough to warrant terminating the program (ERROR). Unfortunately, hibernate seems to take a much more liberal view of WARN. For instance, I see this:
12:25:15,787 (SocketListener-2) [WARN:hibernate.Environment -- hibernate.properties not found]
12:25:20,854 (SocketListener-2) [WARN:impl.SessionFactoryObjectFactory -- no JDNI name configured]
These are not pathological conditions, and it seems to me that INFO would be more appropriate in this setting.
Am I the only one who feels this way? What is the semantic of a Hibernate warning (as opposed to INFO and ERROR)?
Joseph Panico [EMAIL PROTECTED]
_________________________________________________________________
Internet access plans that fit your lifestyle -- join MSN. http://resourcecenter.msn.com/access/plans/default.asp
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
