[
https://hibernate.onjira.com/browse/HHH-2085?page=com.atlassian.jira.plug...
]
Thomas S commented on HHH-2085:
-------------------------------
Apparently this should be an easy fix, but catch-log-then-rethrow is found in more than
one place in hibernate and always considered a minor.
hibernate developers, please consider that hibernate actually is deployed at many sites,
also third party that does not care what technologies used, but who do care when an
exception is logged.
org.hibernate.event.def.DefaultLoadEventListener logs exception at
info level
-----------------------------------------------------------------------------
Key: HHH-2085
URL:
https://hibernate.onjira.com/browse/HHH-2085
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 3.2.0.cr2
Environment: Hibernate 3.2.0.cr2, MySQL 4.0.18
Reporter: Don Smith
Priority: Minor
Prior to schema generation, accessing a persistent object throws an exception, as
expected. The org.hibernate.event.def.DefaultLoadEventListener logs the exception at the
info level, which just adds noise to the application console, and prevents application
exception handling (in my case it's valid if the table doesn't exist, so I just
want to catch the exception and continue). This log statement should be removed, or moved
to a debug or trace level, so it won't show up in normal execution.
Code, from line 94 of org.hibernate.event.def.DefaultLoadEventListener:
catch(HibernateException e) {
log.info("Error performing load command", e);
throw e;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira