I moved
hasConstraints() to the ElementDescritpor
which means that BeanDescriptor, PropertyDescritpor do inherit from
it. Make sense.
I also added a isBeanConstrained() to BeanDescriptor to know if a
given class will be impacted by validation (namely if any of it's
field, method or class /
David, perhaps you could hop on irc and we could discuss this sometime?
The channel is #hibernate-dev on irc.freenode.net
I am in the midst of some pretty significant changes to how hibernate
constructs SQL which will affect (and simplify I hope) the criteria
code.
-
Steve Ebersole
Project Le
The next version of Hibernate Validator will be Bean Validation based
and contain a bridge to support legacy Hibernate Validator.
I am wondering about the version number.
We have three approaches:
- name it 4 but still make it work with Hibernate 3 platform
(waiting for the 4th coming)
-
>
> BTW, what does do?
>
> --Hardy
Hope the spec is not going out with the typo in "inheritance".
We discussed about it here : http://forum.hibernate.org/viewtopic.php?t=985463
It is meant to disable inherited contraints, for when you may want to
define some different
constraint in subclasses ov
Hi,
Should the ignore-annotation flag be a level attribute only
or should a user be able to define it at the field/method/class level?
I think bean level annotation is sufficient. I am sure that some people
can come up with some sort of use case field and method level, but it just
adds unnec
