Ok thanks guys, will try this approach now.
Ben Acker wrote:
I am using a similar approach to Phillip, but using the same method
name for
each page. We have the method implemented in a base page that is
extended by
the pages implementing the component. Anytime we need the method to do
something different, we just overwrite it in that page.
On 5/14/07, Phillip Rhodes <[EMAIL PROTECTED]> wrote:
You can you use IListener as a parameter. On each page, you can bind
your
component to the specific page listener that you want invoked.
This works good, as I am using this approach myself.
----- Original Message -----
From: "Paul Stanton" <[EMAIL PROTECTED]>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
Subject: expert needed
Tapestry 4.1
I've got a set of anchors (<a>) which are common for a group of pages
and are contained within a component, however on each page they need to
do different things. Essentially they will either submit a form on the
page with or without client side validation or perform a simple page
link.
Can I achieve this with a common component with event handling
implemented on a page by page basis, or will I have to re-write the
links for each page?
Thanks for any hints.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
