[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3486) Include one ore more SLF4J "adapters"

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=c... ] Sam Douglass commented on HHH-3486: ----------------------------------- I'm honestly sorry to comment again now that this has been closed, but I do think Hibernate is less usable out of the box without an SFL4J binding than it was without a log4j.properties. Log4j would not throw any NoClassFoundErrors if its properties file was missing. But with SFL4J, if there isn't a binding jar in the classpath to provide the StaticLoggerBinder class, org.hibernate.cfg.Configuration can't even be loaded, because it references LoggerFactory, and LoggerFactory can't be initialized because the StaticLoggerBinder class can't be found. And that's even without any Hibernate logging enabled. SFL4J does print out a URL where you can figure out what's going on, which should be enough to figure out how to proceed. It might be even more helpful if the "one and only one" binding requirement were worked around, by having the LoggerFactoryBinder implementation classes in the binding jars have unique class names instead of all being named StaticLoggerBinder, then using a property to configure which implementation class to load. That way there could be a default that users could optionally override. Anyway, this isn't the SFL4J bug tracker or mailing list so I know that sort of suggestion isn't appropriate here. Sorry to have stirred up a bee's nest but hey, at least this issue is closed now. ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira