Certainly. But in this case it's a good match to the desired semantics, reduces code, and reduces potential coupling between the model and presentation. If it works again...
Jeff Bischoff wrote: > > There are cases where I find the "required" attribute to be cumbersome. > Whenever that occurs, I just move that check to my action methods. Don't > know if that will make any difference in your case, but don't feel like > you *have* to use required just because the spec provides it to you as > an option. :) > > fastbob wrote: >> We want the >> "nothing has been selected" representation to force an error, either >> through >> required="true" or some other mechanism. >> > > > > > -- View this message in context: http://www.nabble.com/ERROR%3A-Value-is-not-a-valid-option-tf3270984.html#a9821363 Sent from the MyFaces - Users mailing list archive at Nabble.com.
