Handling of multiple onActivate methods could be improved.
----------------------------------------------------------
Key: TAPESTRY-1695
URL: https://issues.apache.org/jira/browse/TAPESTRY-1695
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.5
Reporter: Nick Westgate
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
