[
https://issues.apache.org/jira/browse/TAPESTRY-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1730.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.6
This order is determined by the compare() method of TransformMethodSignature;
it is now set up to sort ascending by name, then descending by parameter count
(within a single name).
> Order of event handler method invocation should be greatest number of
> parameters to fewest
> ------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1730
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1730
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.6
>
>
> Say you are writing an activate event handler, meant to guard the page
> against access without a provided token.
> void onActivate(String token) {
> // validate the token
> }
> Object onPassivate() { return _token; }
> Great ... but what about the case where the user omits the token?
> Object onActivate() {
> return _invalidAuthorizationPage; // Redirect away
> }
> But with the current setup, this gets invoked BEFORE onActivate(String) so
> there's no hope of actually using the page, even with the security token.
--
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]
