just read

http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk7.html

well its not bad, but most of the stuff the guy wrote i was already ware of. and where the hell we get to if i have to reimplement phasecallback listeners in jsf ?
by the way, the id of the ui component which is invalid is anyway included in the new jsf facesmessages. i also get it easily done to display an icon next to the invalid field, but how to easily highlight the input field ITSELF???. consider style problems, when showing an icon or even the whole validation message it might bust your layout.
so, the article above does not provide any solution for me. by the way the guys from oracle, maybe his adf components are really as powerful as he says, honestly i doubt it.

@jamie: worked with icefaces as well, really nice, though im not really into its validation mechanisms and wether they do better than the ones of richfaces, which we migrated to from icefaces after having problems.

Cheers.

its definitely rubbish by jsf not to invoke validation on empty inputs.
im currently concerned to create a validation which immediately marks invalid fields on onblur events. this means, when you leave the field the value is submitted via ajax and checked against domain model validation (hibernate validators). this results in less code in the view( no required attributes or defining error messages in the view) and immediate feedback to the user (e.g. highlighting the incorrect field). now i came across a strange thing:
if u use notempty or notnull hibernate annotations on a field (class variable) the validation gets invoked even if the input is null or empty. as hibernate also allows annotation on method level (very useful if you dont have an own field for each setter) i tried to add notempty resp. notnull annotations to the setter of my property. now the validation is not invoked anymore…..how stupid is that.
if anyone knows a solution for that one he gets a big hug (introducing a class variable which corresponds to the setter isnt one )….
so, after years of webdevelopment, there still no proper, user friendly and developer friendly validation framework working…isnt that poor.

greetz

Firstly – simple check on empty fields can be done with converters – they, in turn, will always get called, even if nothing is entered. Pretty simple, huh?

Secondly – if you want to introduce a nonstandard, application-wide behavior on conversion/validation that is not doable using available JSF tags, like changing field classes on errors, start working with JSF phase-aware callbacks, like this one:
http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk7.html
They let you find all the fields that have validation/conversion messages assigned and do whatever you like with the fields and messages alike.

I want to write my own Required Field Validator but can’t as I can’t get it to trigger.

Being able to set a “required” message is not enough, and not very flexible.

I for example, if not valid, set a red border around the text field that is invalid by adding a css style. I can’t do this with the inbuilt required field validator.

I’m a .Net developer, but have been playing around with JSF and quite enjoying it. This is quite a poor design flaw. As is not being able to get a textbox’s associated label (at least in an easy way).

I’ll post a fix if I find one.