Thanks for the link. So, I wrapped my drop-down boxes in a <tr:subform> and the other components in one as well. Now, validation doesn't occur on the other components, but changing the drop-down box values no longer works. After I change a drop-down value, the resulting phases are:
Restore View --> Apply Request Values --> Render Response Why should wrapping the drop-downs in a subform cause the Process Validations, Update Model Values and Render Response phases to be skipped? Thanks for your help, --David --- Mike Kienenberger <[EMAIL PROTECTED]> wrote: > http://incubator.apache.org/adffaces/trinidad-api/tagdoc/tr_subform.html > > On 4/18/07, D. Cardon <[EMAIL PROTECTED]> > wrote: > > Hi all, > > > > I have a page in which I use a partial refresh to > > update selectable values in some drop-down boxes. > In > > this scenario, the values in one drop-down > determines > > the set of possible values in another drop-down. > So, > > a partial page refresh seemed an intuitive way to > > handle the update of the dependent drop-down. > > > > In addition to these drop-down boxes, there are > other > > components on the page, some of which need > validation. > > However, I would only like to validate the > components > > when the form is "actually" submitted--not during > the > > autoSubmit of my related drop-down boxes. Is > there > > any way to detect the partial page refresh during > the > > validation phase and prevent the validation from > > occurring? Or is there a better way to handle > this? > > > > Thanks, > > > > --David > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
