yeah, i ended up doing something similar. i created a @SuppressValidation component which you can wrap around some fields in a form which will temporarily ignore validation errors using a custom validation delegate. :)
On Thu, 2006-07-13 at 21:40 -0400, James Carman wrote: > Don't put a listener on the form itself and put one on the submit button (or > @LinkSubmit or whatever). That's what I'm doing. I am implementing my own > validation delegate which only displays error message indicators if its > "validated" flag is set (which I do in my "submit" button listeners). > > -----Original Message----- > From: Dan Adams [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 13, 2006 9:37 PM > To: Tapestry users > Subject: Re: suggestions on a conditonal render in the rewind > > Perhaps I could phrase it another way. I've got a set of fields that I > only want to be validated against when a particular submit button is > clicked. Any ideas? > > On Thu, 2006-07-13 at 21:30 -0400, Dan Adams wrote: > > Okay, I've got a component that is used in a form and basically to solve > > some validation problems i need to have the component not render a > > couple form fields when performing validation based on which submit > > button was clicked. my question is, have people had experience with this > > and what's the least problematic way to do it? the tapestry docs say > > that using @If with volatile=true can cause problems. How are these > > problems manifested? Thanks in advance for the suggestions/comments. > > -- Dan Adams Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
