[
https://issues.apache.org/jira/browse/TAPESTRY-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAPESTRY-1295:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> More leniency needed in onActivate( ) method matching
> -----------------------------------------------------
>
> Key: TAPESTRY-1295
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1295
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0
> Reporter: Daniel Gredler
> Assigned To: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0
>
>
> 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."
--
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]
