Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Steve, I think there is something fishy. I have created a branch with a blatant usage of a JDK 8 API in hibernate-core There is one commit above today’s master: protected EmptyInterceptor() { + final java.time.ZoneId id = java.time.ZoneId.systemDefault(); + Sys

Re: [hibernate-dev] document update change?

https://github.com/infinispan/infinispan/commit/2d299745df1ce83c23ddc63e066ee820c184b8a7 > On 03 Apr 2015, at 12:38, Ales Justin wrote: > > OK, found the culprit ... > > It is this "weird" rule -- why n

Re: [hibernate-dev] document update change?

OK, found the culprit ... It is this "weird" rule -- why not remove if the value class is the same?! private boolean shouldRemove(Object value, Object previousValue) { return !(value == null || previousValue == null) && !value.getClass().equals(previousValue.getClass()); } in --- private voi

Re: [hibernate-dev] document update change?

I think the problem is in our SearchWorkCreator, and how HS doesn't provide old value when doing update (while doing delete). * https://github.com/capedwarf/capedwarf-blue/blob/master/datastore/src/main/java/org/jboss/capedwarf/datastore/CapedwarfSearchWorkCreator.java