[jira] Updated: (TAPESTRY-1295) Event handling methods that have too many parameters for the event context should be silently skipped

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-1295:
-------------------------------------------

      Component/s: tapestry-core
    Fix Version/s:     (was: 5.0)
         Priority: Major  (was: Minor)
          Summary: Event handling methods that have too many parameters for the event context should be silently skipped  (was: More leniency needed in onActivate( ) method matching)

> Event handling methods that have too many parameters for the event context should be silently skipped
> -----------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1295
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1295
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0
>            Reporter: Daniel Gredler
>         Assigned To: Howard M. Lewis Ship
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org