[TAP5-597] The form submit event handler method should have access to the source of the event

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Component/s: tapestry-core
• Assignee: Unassigned
• Reporter: Hugo Palma
• Created: 25/Mar/09 13:42
• Updated: 25/Mar/09 14:05
• Resolved: 25/Mar/09 14:05

Description

Right now if you want to have more than one submit button in a form and you want to implement different execution logic for each you have to:

• implement an event listener for both buttons that sets a local field that signals which button was pressed.
• implement a form event listener method that reads the local field value and executes whatever logic based on that.

(such a solution is provided on http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/input/multiplesubmits1)

If the form event listener could know which button triggered the commit this type of logic would be much simpler to implement.

Issue Links

• duplicates: TAP5-146 Provide some way to get the component that fired an event