Validation

As far as quantity of validation is concerned, I don't see that it makes a
difference where it is done. There are various technical reasons why you
might want to do a particular validation on the client or on the server, but
as long as it gets done in at least one place, I don't have a problem with
it.

For example: suppose your client has an HTML form that asks you to enter a
product number. Where should you validate that? If it requires a database
lookup, and your server program is already accessing the database, then the
server should do the database lookup. Should the client pre-validate it,
using Javascript, to check that what was entered was a number and not zero?
It's possible, but then you have two different styles of error message being
presented to the user. A system designer might reject that possibility and
opt to have all validation on the server, resulting in consistent
presentation of error messages.

Marcia <isoint@msn.com> wrote in message news:39bfda61@news.devx.com...
>
> I'm just starting with Java and my first duty is to do the validation for
> the application.
> The group I'm working with wants to have a server side validation and not
> client side validation with Java Script.
> Well I'm a back end programmer in VB, and C++, in my experience a safe and
> reliable application must have both client and server validation.
> Can someone clarify to me why my group believes that just server
validation
> is enough, or I'm wrong and a 100% java application does not need client
> validation.
>
> Thanks
>