Re: Client en Server side validation

2011-01-20 Thread Jeroen Wolff
I've got 2 types of validation. Syntax and business rules. The syntax can be solved in the presenter, but i don't want to validate the whole bean if i only want to validate one property of that bean. I'm thinking to make it like this: Class Foo() { Date date; String otherfield; public

Client en Server side validation

2011-01-19 Thread Jeroen Wolff
Hi, there has been a lot of discussion already in this group about validation and the frameworks that can help with it. Now i'm in a big project which need form/field validation onChange focus events and the same field validation need to be done on the server when the domain objects are being send

Re: Client en Server side validation

2011-01-19 Thread Ben Imp
The correct thing to do, in my mind anyway (admittedly an odd place), is never trust a client and do your own validation of the data and operation requested. This contrasts with my professional experience, which has been that pretty much everyone just trusts the client and mindlessly follows its

Re: Client en Server side validation

2011-01-19 Thread Jeff Schwartz
It depends on what you mean by validation. If you mean that the data conforms to the business rules then IMO you can validate on the client and all you need to do on the server is authenticate the user. A practice that I follow is storing the user's session id in encrypted form on the client. I