Paul, I apologize for recommending a 'dirty' way of solving your problem!
You could just create a new component based on the AbstractSubmit class or the Submit component. That way you could utilize the form submission from AbstractSubmit. In addition, the html in your tab could display this new component when within a form, or a direct link when not requiring a form submit. That way it should work and stay clean. Or you could modify a Submit button using CSS so it looks like a normal link, but make sure that your tabs on pages w/ forms reside within the form. -Ben On 5/23/07, Nick Westgate <[EMAIL PROTECTED]> wrote:
Paul Stanton wrote: > Hmm.. I guess what I don't get is how you can submit a form from a > DirectLink component. I'm guessing you can't, unless you emulate what LinkSubmit does: http://tapestry.apache.org/tapestry4.1/components/form/linksubmit.html In my Tapestry 3 apps I actually used form submits exclusively exactly because of the problem you're having. Any link or button press should preserve form data and then validate or navigate. I structured this by having a form in my Border component, and the base class for all pages providing the "root" listener. Every link assigned a string which the listener processed. Each page handled it's own action strings ("save" etc) and the root listener handled various global actions like navigation (E.g. "_PageName"). Cheers, Nick. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
