My first attempt to solve such a problem was to create the OptionalValidationFramework discussed on the wiki, but I don't really like that approach. It worked for me because I had a lot of dropdowns on the page.
You might take a look at using the Sandbox subform validation as an alternate way to do optional validation. If you have only a few components that need to work like this, you could manually perform the update model phase yourself. I haven't tried it, but you might be able to call component.processUpdates() in your handler. Otherwise, you can manually grab the submitted or validated local value from the component, and manually put it into the backing bean. On 3/23/06, Yura.Tkachenko <[EMAIL PROTECTED]> wrote: > > Ok, Thanks. Do you know any solution which will be usefull for me? > > Thanks, > Yura. > > -----Original Message----- > From: Mike Kienenberger [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 23, 2006 6:42 PM > To: MyFaces Discussion > Subject: Re: Skip Validation Phase > > On 3/23/06, [EMAIL PROTECTED] > > I know this, but for skip validation phase I'm using call: > > FacesContext context = FacesContext.getCurrentInstance(); > > context.renderResponse(); > > I guess I was too subtle. > > You're not skipping just the validation phase. You're skipping all > phases after ApplyValues, including UpdateModel. Your backing beans > will not be updated. > >
