> >You are misunderstanding the entire SLF4J/Logging paradigm. You don't tell >Hibernate (or SLF4J) what to log - you tell the logging backend what to do >with the messages Hibernate logged. And to do that you need to configure the >logging backend.
The misleading path is probably that in EclipseLink, there are options <property name="eclipselink.logging.level" value="INFO" /> <property name="eclipselink.logging.level.sql" value="FINE" /> to tell the ORM what to log, so I'm not as far off the track as you might think. I had hoped for a similar option in Hibernate. (I'm indeed not a fan of logging so far.) I don't necessarily want to dump *all* incoming INFO level messages, just the ones that Hibernate produces. This appears to be impossible now. > >> I disagree, because Hibernate causes all the INFO log entries and it >> DEPENDS on SLF4J. My choice for the JDK logger was purely for >> simplicity. However, there must be a way to tell Hibernate to only log >> starting from warning level. That's what I want to know. Configuring >> the JDK logger here doesn't make much sense because Hibernate will use >> whatever I have chosen. If I switch to another SLF4J logger >> implementation then the same problem would reappear, so your answer >> isn't really helpful. >> >_______________________________________________ >slf4j-user mailing list >[email protected] >http://qos.ch/mailman/listinfo/slf4j-user ___________________________________________________________ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02 _______________________________________________ slf4j-user mailing list [email protected] http://qos.ch/mailman/listinfo/slf4j-user
