But you never see these classes unless you implement the spec. And if
you implement the spec, I don't care how hard it is for you.
ValidatorBuilder is an essential feature used by JPA and JSF so that's
a no go.
On Jan 16, 2009, at 09:09, Hardy Ferentschik wrote:
On Thu, 15 Jan 2009 16:24:
On Thu, 15 Jan 2009 16:24:34 +0100, Emmanuel Bernard
wrote:
I am still not
convinced that the whole API fis not overcomplicated
Which step is too complicated and need simplification. Any example?
I just think there are too many levels of indirection. When I look at the
example on how to
On Jan 15, 2009, at 04:05, Hardy Ferentschik wrote:
I am still not
convinced that the whole API fis not overcomplicated
Which step is too complicated and need simplification. Any example?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
Hi,
I think the name changes are definitely a step into the right direction. I
am still not
convinced that the whole API fis not overcomplicated, but if we go down
this path I give
the new names a +1. Changing ValidatorFactoryBuilder to Configuration is
also a good idea
since I believe we h
The naming in the bootstrap API was lacking some consistency and was a
bit obscure at time
I went back tot he drawing board and came with something that is I
think more natural and thus easier to use:
- to build ValidatorFactory
- to build Validator
Each set of proposal change is followed
