Right, you can have optional converters, although it's not well supported yet as the only optional converter I've had need of was the one used internally for inputCalendar, and that's a no-arg converter for my use-cases.
Any time either conversion or validation is skipped or errors are ignored, the backing beans won't be updated, but that's just the nature of the beast. If you can't get the data, you can't save it :) It's the responsibility of the end-developer to check to see if the data is in a valid state before trying to use it. However, we haven't had any luck getting JSF1.1 validators/converters working with our framework. For the framework to be useful, you have to use facelets or upgrade to JSF 1.2 so that validators/converters are restored rather than recreated between requests. I also haven't gotten to the point of allowing different validation options depending on which button is pressed, although it's on my eventual todo list. On 12/22/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Matthias is absolutely right here. > > He can't bind the value to the backing bean, as he doesn't want > conversion and validation to happen. Binding the component to a > session bean sounds like an interesting solution - have never thought > about this before... > > Conversion and validation with different buttons to happen and others > not is actually a week point of JSF - I like what Mike and Jesse have > done with their optional validation framework so far, though. But even > with this framework, you can't do anything about conversion, right? > > Mike, you have soft converters, too, but if a string doesn't convert > to a date correctly, you can't set it to the backing bean, right? > > regards, > > Martin > > On 12/22/05, Matthias Kahlau <[EMAIL PROTECTED]> wrote: > > > > > > > OK, now I'm lost ... why would you want to skip the update model values > > phase? > > > > Because I have to skip the process validations phase, so that the user's > > work flow isn't broken. The user just wants to edit some details on a sub > > form, and then return back to the main form. Validation of the main form > > should only occur at the end of the user's task, when he presses the save > > button on the main form. > > > > > > > > > > On 12/22/05, Matthias Kahlau <[EMAIL PROTECTED]> wrote: > > > > > > Hi Craig! > > > > > > I think you don't mean the *value* attribute of the component tag, because > > as I know, this is not possible in my use case. The related backing-bean > > property won't be updated, since the update model values phase is skipped. > > The value entered is stored in the component (submitted or local value) > > only. > > > > > > > > > > > > > > So what do you mean with "binding the *value* of the component to a > > session bean property"? > > > > > > Yes, binding the value property is what I was referring to. > > > > > > > > > > > > Regards, > > > > > > Matthias > > > > > > Craig > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
