It might be nice to be able to have multiple onActivate( ) methods on a page, each handling a different number of context elements (including none).
Howard's comment on the mailing list (http://www.nabble.com/T5%3A-onActivate-error-handling--tf3281698.html):
"I'm thinking the change will be: a method will be invoked if the
context has at least as many values as the method has parameters, and
will silently skip those that request too many."
|Workflow||Default workflow, editable Closed status [ 12567756 ]||jira [ 12590884 ]|
|Workflow||jira [ 12398179 ]||Default workflow, editable Closed status [ 12567756 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||5.0.3 [ 12312338 ]|
|Fix Version/s||5.0 [ 12312018 ]|
|Summary||More leniency needed in onActivate( ) method matching||Event handling methods that have too many parameters for the event context should be silently skipped|
|Component/s||tapestry-core [ 12311285 ]|
|Priority||Minor [ 4 ]||Major [ 3 ]|
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|