[ 
https://issues.apache.org/jira/browse/WICKET-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447026#comment-13447026
 ] 

Ota Hauptmann commented on WICKET-4739:
---------------------------------------

You are right, it is correct in 6.0.0. Sorry for that, but I didn't noticed 
this version is released (not mentioned on wicket home page). So you can 
probably close this issue. But...

There is still the problem, which led me to report this issue. This problem is, 
that if there is an Ajax link which causes a redirect (if there is an exception 
or redirect to login page), only the complete handler is called. No call to the 
success handler (which wouldn't make much sense), but also no call to the 
failure handler. But as I said, the complete handler is called. I understand 
the documentation in the way, that in all cases either success or failure 
handler should be called and then the complete handler. But in this situation 
no success or failure handler is called.

So is this a feature or bug? Is it known? I didn't find such issue, which is 
open. Should I report it? If it is necessary, I can attach quickstart example 
of this issue, it is quite trivial to simulate it.

Thank you for your answer.
                
> Complete handler called before success or failure handler (not after them, as 
> documented)
> -----------------------------------------------------------------------------------------
>
>                 Key: WICKET-4739
>                 URL: https://issues.apache.org/jira/browse/WICKET-4739
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.0.0-beta3
>            Reporter: Ota Hauptmann
>
> When registering an Ajax call listener, complete handler is called before 
> success and failure handler. In documentation, the order is opposite.
> When registering the global Ajax call listeners, the order is correct (as 
> documented). So both these cases are inconsistent - one follows the 
> documentation, one does not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to