Hi,
I like the idea. Emmanuel's performance test showed an execution time per
validation of 11 vs. 74 ms on my system, so there seems to be some
potential. Instead of having a "failFast" flag one could also introduce a
numeric parameter to control, when validation should stop. A value of "1"
would
That or slowish validations.
One typical use case is that:
if ( validator.validate(customer, StraightToValidationScreen.class).size() >0 )
{
//manual process
}
else {
//automatic process
}
BTW, I've committed a non scientific perf test that shows an average of 5x perf
improvement on an obj
Ah, I had tried void and voic.class. Did not know about Void.class. Good to
know. I will change that
On Monday, October 04, 2010 09:59:14 am Emmanuel Bernard wrote:
> Not commenting on the idea of an Hibernate specific registry, here are a
> few comments on the design:
>
> Map should be Map
I remember Mark P. mentioning they (drools) have some basic bootstrap for their
core which is simplistic and then if containers want it can use another DI to
set it up for user visibile customization (i.e. spring, cdi etc.)
Not sure how they did it though - but might be worth a look ?
/max
On
Not commenting on the idea of an Hibernate specific registry, here are a few
comments on the design:
Map should be Map or whatever types will end up being used.
public Class serviceRole() default InjectService.class;
should probably be
public Class serviceRole() default Void.class;
Void.class
What would be the usecase? Saving time in large object graphs where I am
only interested in whether there is a
failure at all? You really need LARGE object graphs to make this worth
while.
On Mon, 04 Oct 2010 15:45:34 +0200, Emmanuel Bernard
wrote:
> http://github.com/emmanuelbernard/hibe
Fixed.
Sorry about that.
On 4 oct. 2010, at 15:54, Hardy Ferentschik wrote:
> Jupp, that's a bug. It should use StringHelper.isEmpty()
>
> --Hardy
>
> On Mon, 04 Oct 2010 15:38:52 +0200, Scheper, Erik-Berndt
> wrote:
>
>> Just for the record: this is not for Hibernate 3.6 is it?
>>
>> The
Not a simple one I am aware of. There is seam/weld/cdi which is more than we
need. And I have been unable to find "real life" microcontainer use guides for
something like this. Bear in mind that my bootstrap class is simply one
choice/option to this. The services at the end of the day are ju
On 10/02/2010 06:39 PM, Steve Ebersole wrote:
> https://sourceforge.net/apps/mediawiki/hibernate/index.php?title=Category:Services
Isn't there a service-lifecycle-and-dependency-injection library in our
arsenal we can use?
-CB
___
hibernate-dev mailing
On 10/01/2010 07:57 PM, Steve Ebersole wrote:
> The vast majority of databases out there have more or less decent JDBC
> drivers. So forcing every single Dialect to reproduce information that
> is already correctly available to us because of a few *known* slackers
> seems silly. Why can't the maj
Thanks Gunnar. I'll have a look at it and come back to you.
On Mon, 04 Oct 2010 00:32:27 +0200, Gunnar Morling
wrote:
> Hi,
>
> I pushed a first rough draft for the method-level validation to GitHub at
> http://github.com/gunnarmorling/hibernate-validator/tree/method-level-preparations
>
> Cu
Jupp, that's a bug. It should use StringHelper.isEmpty()
--Hardy
On Mon, 04 Oct 2010 15:38:52 +0200, Scheper, Erik-Berndt
wrote:
> Just for the record: this is not for Hibernate 3.6 is it?
>
> The reason I'm asking is that I get a build failed in my local build of
> AnnotationBinder.java, l
I wanted to make it explicit that this is not the initiator's type/role. Its
the role/type of the service being initiated. I do not follow how you infer
"get me the service initiated" to mean a method for doing the initiation.
Given the vocabulary that has sort of grown, I'm ok with saying
g
>> Totally agreedI guess the question is though if that is going to part of
>> what we
>> today call Dialect or something else (If i follow Steve's comments right)
>
> The vast majority of databases out there have more or less decent JDBC
> drivers.
Actually, that ain't true when it comes t
Nice.
One comment, I think ServiceInitiator.getServiceInitiated() is a little
confusing. Just by then name I thought
it would be the method which initiates the service, but it rather just
gives me the service type/name.
Why not ServiceInitiator.getServiceType?
--Hardy
On Sun, 03 Oct 2010 00:
http://github.com/emmanuelbernard/hibernate-validator/commits/failFast
What do you guys think?
The idea is to stop a the first failure.
You can enable that :
- by property
- at config time
- when the Validator is created
Look at
http://github.com/emmanuelbernard/hibernate-validator/blob/fail
Just for the record: this is not for Hibernate 3.6 is it?
The reason I'm asking is that I get a build failed in my local build of
AnnotationBinder.java, line 2664, where string.isEmpty() is added, which is
only available since JDK 6.
Kind regards,
Erik-Berndt
__
17 matches
Mail list logo
