I am finding that the UI design for a particular page that the client is requiring is causing me to have a headache in regard to tapestry validation. It would not be a problem if I could just separate the functionality into 2 different forms....
I have a checkout page that has a required validator working for credit card information (credit card number, bill address, date, etc). In the same form, there is a field for customers to input gift certificates, promotion codes, etc.. as payments. There is "Enter Another" submit button along with this field that invokes a "enterAnother" listener. This listener will read the field and enter that as a payment for their order. Customer have the ability to just enter the one promotion code they have into the form and proceed in the checkout. The problem occurs when one submits a enterAnother listener, the validation for the entire form is triggered. While I understand that I could disable this validation by binding the required flag to a page property, I can simultaneously bind one submit button to both a listener and a page property. Anybody have any ideas how I can solve this problem? Thanks. BTW, This cart I am working on is soon to be released with an apache open-source license. It has 120 db tables (already) and over 1meg of compile binary code. While code/table numbers do not measure quality, they do measure my effort. Features include portal/cms/sso . Tools are tapestry/lucene/hibenate. Seeking help! Send an email.... I also need a cool name for it;) It will be professional-grade. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
