Dave,
i am agree with you, i just followed doc and than it started giving me some
strange issues in validations.
I tried to debug underlying API but with no success.
On doing some more Googling i came across create new instance outside
getModel() and it started working as expected.
Thanks
Umesh
Wouldn't this return a new ProfileDTO every single time getModel() is
called?
This, in turn, would mean that if you were validating model.foo and
model.bar that it'd be called twice.
I have not verified this, perhaps there's some magic (e.g., spooky) caching
happening somewhere, but to my mind, w
> Just to add more information by changing code to
>
> ProfileDTOgetModel md=new ProfileDTOgetModel();
> @Valid
> public ProfileDTOgetModel()
> {
> return md;
> }
> }
>
> Bean Validation is working fine, so i am confused which is right way to
use
> Model driven.
> I took ref
Just to add more information by changing code to
ProfileDTOgetModel md=new ProfileDTOgetModel();
@Valid
public ProfileDTOgetModel()
{
return md;
}
}
Bean Validation is working fine, so i am confused which is right way to use
Model driven.
I took reference from
http://struts.
No, my issue is something different..
some how underlying Valitor API is not validating all fields and its
happening only when i am using Model driven, for rest cased everything is
working fine for same bean object and for same validations.
On Tue, Oct 15, 2013 at 3:15 PM, Christoph Nenning <
chr
5 matches
Mail list logo
