validation.valid(key, object) should support null - null key - no prefix would be added

[tomas]

It would be nice if there was a way not to add the prefix to the validated object:

Person person=new Person(name)
validation.validate(null, person); // would add Error with key 'name' instead of 'person.name'

Fix:ValidCheck:50
from
String fkey = key + "." + ctx.getField().getName();
to
String fkey = (key==null?"":key + ".") + ctx.getField().getName();

[Nicolas Leroux (nicolas-lunatech)]

I don't understand the use case I have to say. Why would you want this feature?

[tomas (gugljafa)]

I am not binding parameters to objects in this case, so I have an action method like
public static void foo(@Required String name){ // would add new Error with key 'name'
Person person=new Person(name);
validation.valid(person); // I have another validation in the Person class, so this would add error with key 'person.name'
validation.valid(null, person) would add error with key 'null.name' which makes no sense anyway

I want the ability to unite the two validation approaches easily

[Nicolas Leroux (nicolas-lunatech)]

You are right to say that it makes no sense anyway ;). But I was wondering if it was really the fix or if the valid method was abused. Fixed committed but I find it a bit weird to use valid(null, person). We should maybe come with a better solution. Anyway, thanks.