Client Side Validation for 2.3

[cagatay.civici]

Dear PrimeFaces Community,

I'm wondering if you'd like to see Client Side Validation in 2.3, in the past I've done a proof of concept work on myfaces tomahawk;

http://example.irian.at/example-sandbox ... rdForm.jsf

Personally I'd like to see something similar and much better in PrimeFaces.

Thanks for your feedback,

Cagatay Civici
PrimeFaces Lead

[bardu]

Personally, I would prefer to see PF mobile and Ajax push coming out as soon as possible.

Client side validation can wait until 2.4.

[cagatay.civici]

Yes, this is something after, highlights of 2.3 is Ajax Push and PrimeFaces Mobile.

[bumble.bee]

Client side validation is definately a nice to have. It is an optimization though (reduce server load and speed up user experience).

My vote is to spend extra time making PrimeFaces more stable (and usable). Make sure existing components work well with each other and can be combined in dialogs and such. Also, add features to existing components such as adding subTables to dataTables.

[MISS_DUKE]

Client side validation is not so important as we can do server side validation using Ajax which more or less resembles (in the point of the user) client side validation.

[Oleg]

Hi,

I didn't have a good experience with client-side validation because it doesn't help in most cases. If you use user-specific date / time formats, time zones or something like you need to do a request in order to proper server-side validation. What can you validate client-side? For requiered fields we don't need a client-side validation framework. For masked input we have p:inputMask or can even archieve that with a simple JS reg. expression. Could you say me an example where such validation framework is really needed?

Thanks.

[healeyb]

I'd agree with comments already expressed that client-side validation is
more of an optimisation than anything else, but, and it's a big but, I've
yet to be in a position to see just what the impact of all this ajax is on
a heavily loaded production server. I'd still tend to assume that validation
would only account for a comparitively small proportion of the ajax
overhead though.

Mobile apps are firmly at the top of my list also, and who doesn't rate
stability as a topmost priority.

Regards,
Brendan.

[Oleg]

One reason more against client-side validation: How do you plan to internationalize messages? For multi-language web apps you should keep all validation messages for all languages on the client-side (we want to avoid roundtrips to server). Right? It's acceptable for you to have 300-400 long text in JavaScript object(s)? How do you plan to maintain this stuff? Java property files, in contrast, can be easy sent to an interpreter.

Client-side validation is normally not enough and we should repeat all validation steps on the server-side. One of rules in the web development says - not trust client-side, backend should always do validation as well if the front-end UI technology will be changed in the future or the same backend is used by another clients. Right? That means, messages and all validation related implementations are repeated twice, client-side and server-side. You maybe save an ajax call, but wast time with coding. It's really acceptable for you?

[cagatay.civici]

Thanks for all the feedback, was really helpful. I think we have more to do(e.g. Ajax Push, PrimeFaces Mobile, portlet samples, new components, bug fixes) before thinking about client side validation.

[callahan]

I missed the party here, but I like the outcome.