[TAPESTRY-1695] Handling of multiple onActivate methods could be improved.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.0.5
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Nick Westgate
• Created: 08/Aug/07 10:16
• Updated: 22/Oct/07 16:16
• Resolved: 22/Oct/07 16:16

Description

The summary is vague because the docs don't yet cover this situation.
It seems reasonable to have need for something like:

Object onActivate()

{ ... }

void onActivate(int itemId) { ... }

The current event handling calls both these activate methods (the 0 parameters method first, then others).
I see only two ways of dealing with this:

(1) Factor out common code and use a flag to avoid executing that code twice
(2) Replace the two activate methods with:

Object onActivate(Object[] parameters)

{ ... }

Both options impose some fiddly responsibilities onto the developer.
Perhaps a resolution is already planned but here are some ideas:

• call only one event handler
• allow event handlers to short-circuit (return boolean/Boolean?)
• swallow coercion exceptions so other event handlers can be tried

Cheers,
Nick.