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
