[jira] [Closed] (WICKET-6612) Stateless page, Ajax behavior/component

["Andrea Del Bene (JIRA)" <ji...@apache.org>]

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

Andrea Del Bene closed WICKET-6612.
-----------------------------------
    Resolution: Cannot Reproduce

> Stateless page, Ajax behavior/component
> ---------------------------------------
>
>                 Key: WICKET-6612
>                 URL: https://issues.apache.org/jira/browse/WICKET-6612
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 8.1.0
>            Reporter: Oddgeir Bell
>            Assignee: Andrea Del Bene
>            Priority: Minor
>              Labels: documentation
>
> The documentation for stateless pages in Wicket could be improved.
> One thing we had to look through the javascript source code to figure out, is the following:
> You have an Ajax component (AjaxButton, for example) within a Stateless form, which is itself within a stateless form. You have done setMarkupId on both the inner form and the AjaxButton.
> BUT, if you have a bound session (really not sure why this is an issue, but it is), and you rerender the component, it doesn't work. So, it only works the first time. (In our case, it worked twice, because we did not bind the session untill the user clicked it).
> The only error you get is "Ajax request stopped because of precondition check" in the Ajax Debug Console.
> The problem was that apparently the outer form needs to have setMarkupId too (I assume because the inner form is basically just a div?), which is often not very obvious when you have many nested panels.
> Sadly, it seems that not many people use Wicket stateless, so we have to figure out issues like these without the help of google...
> I'm not sure if this is by design or not, but it would probably help others if it was documented (along with all the other caveats you get with stateless).
>  
> On a brighter not, we seem to have gotten most of our issues with stateless pages ironed out now, and things are looking good.
> Keep up the good work!



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)