i agree, my preference is that these messages should be info, not warn. =
however, hibernate internally uses jakarta commons-logging, so i don't =
quite know how the logging level is controlled with that. i won't have =
a chance to look at it for a couple days.
brad
> -----Original Message-----
> From: Joseph Panico [mailto:joe...@ho...]
> Sent: Tuesday, 29 October 2002 3:28 AM
> To: hib...@li...
> Subject: [Hibernate] semantic of log WARN
>=20
>=20
> Hello,
>=20
> (I'm using hibernate-1.1)
>=20
> I'm integrating a lot of different frameworks that all use=20
> log4j as their=20
> logging mechanism. In all of the other frameworks, WARN level=20
> messages are=20
> reserved for "pathological conditions". They indicate that=20
> something is=20
> seriously out of whack, but perhaps not seriously enough to warrant=20
> terminating the program (ERROR). Unfortunately, hibernate=20
> seems to take a=20
> much more liberal view of WARN. For instance, I see this:
>=20
> 12:25:15,787 (SocketListener-2) [WARN:hibernate.Environment --=20
> hibernate.properties not found]
> 12:25:20,854 (SocketListener-2)=20
> [WARN:impl.SessionFactoryObjectFactory -- no=20
> JDNI name configured]
>=20
> These are not pathological conditions, and it seems to me=20
> that INFO would be=20
> more appropriate in this setting.
>=20
> Am I the only one who feels this way? What is the semantic of=20
> a Hibernate=20
> warning (as opposed to INFO and ERROR)?
>=20
> Joseph Panico
> joe...@ho...
>=20
>=20
>=20
> _________________________________________________________________
> Internet access plans that fit your lifestyle -- join MSN.=20
> http://resourcecenter.msn.com/access/plans/default.asp
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>=20
|
