Hey, guys,
I created the simplest hbm mapping and try to build session factory(full
project attached, Hibernate-core4.0.0.CR6):
/new MetadataSources(
new ServiceRegistryBuilder().configure()
.buildServiceRegistry()).buildMetadata().buildSessionFactory();/
As part of a fix for HHH-5222, I changed LockMode.OPTIMISTIC +
LockMode.OPTIMISTIC_FORCE_INCREMENT to be higher values than
LockMode.READ. This helps the case where the user starts with a READ
lock and later upgrades to LockMode.OPTIMISTIC_FORCE_INCREMENT.
Previously, we would of only handled
The solution is really easy guys:
log.debugf("The thing I want to log is %s", thing);
or
log.debug(thing)
In addition, as you have noticed, it is better to not use the formatting
variants if you aren't actually formatting any strings (it doesn't make
a difference if the message isn't logged, bu
I am going to put releasing 4.0.0.CR7 until after the Thanksgiving
holiday. So rather than 11/23, it will be done 11/30.
Sorry for any difficulties.
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.
Hi,
this revives my email from Friday
(http://lists.jboss.org/pipermail/hibernate-dev/2011-November/007307.html)
where I noticed this problem as well.
Generally speaking Sanne is of course right and the right logging method
should be used,
but does the logging framework really have to propaga
On Nov 23, 2011, at 11:34 , Sanne Grinovero wrote:
> log.debugf vs log.debug
> log.tracef vs log.trace
This also seems to be the difference between these messages with JUL:
[main] TRACE - 11:27:51,428 - org.hibernate.loader.Loader:
org.hibernate.internal.CoreMessageLog
Hi all,
I'm having a chat with Hardy about how we used the Logger in some
cases, and it turns out there's some confusion about
log.debugf vs log.debug
log.tracef vs log.trace
So the "F" variant is needed when we want to format a message, in this
case we should make sure the number o
