Hi Hardy,
could you not use a single object parameter to which you add all
fields you need? ThreadLocals are never a good idea imho, I'd use it
only if you have no other choice (like can't break some API). It took
some time to remove them from Infinispan, much better now.
Is it just these two eleme
Hi,
I think a good start for HV-439 would be to check for superfluous type
parameters. There a several parameterized methods in ValidatorImpl
which have unnecessary type parameters (mea culpa). I think
ValidatorImpl will look much simpler afterwards.
Regarding the ThreadLocal, I'm not sure. This
Hi,
I was thinking about https://hibernate.onjira.com/browse/HV-439 which basically
also means a
refactoring of the current ValidatorImpl.
One thing I noticed is that we start at one of the public Bean Validation
methods and then
create different context (e.g. ValueContext, ValidationConext) wh
the jbott logging bot was not around today, so i just captured the
discussion an have attached it here.
Essentially:
1) 4.0.1 release on 4/11
2) after 4.0.1: (a) rename repo; (b) branch 4.0
3) 3.6.10 in 4 weeks (2/8) along with 4.0.2 or 4.1.0
4) intructions on handling repo rename to follow
--
I'm looking into it…
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
