[jira] [Updated] (WICKET-5578) Stateless/Statefull pages - incorrect behaviour

["Ilia Naryzhny (JIRA)" <ji...@apache.org>]

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

Ilia Naryzhny updated WICKET-5578:
----------------------------------

    Attachment: wicket5578.zip

Please find quick start is in attachment.

You can find "special" stateful component on HomePage which is making loginin impossible because of explained by me earler reasons.

You can:
1) Either comment line HomePage#62
2) Or remove component "ajaxLink" from the page
to make logging process to work perfectly.

> Stateless/Statefull pages - incorrect behaviour
> -----------------------------------------------
>
>                 Key: WICKET-5578
>                 URL: https://issues.apache.org/jira/browse/WICKET-5578
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.15.0
>            Reporter: Ilia Naryzhny
>              Labels: stateful, stateless
>         Attachments: wicket5578.zip
>
>
> Please advise how to do in following situation or confirm that's a bug and should be fixed.
> There is a page (login page) with stateless form. That page has lots of common components (menu and etc.). There are some statefull components in the components tree that are visible only for signed in users: but once user isn't signed in - that components are hidden. That's why page is becoming "stateless" (no visible components) and form prepared correspondingly. But when form data is submitted: during obtaining of form component to process request - wicket things that page actually is statefull. As a result - page've been recreated and fully rendered - instead of processing of the form.
> There is a workaround: setStatelessHint(false). But imho reason is a little bit another:
> 1) After constuction of page: page is statefull - because of some statefull components are in the tree.
> 2) After initialization of page: page is still statefull - because there are that statefull components
> 3) After configuratoin of page (method onConfigure) - page is becoming stateless - because all statefull components marked as invisible.
> 4) Form has been rendered as stateless - with no version number is in the URL.
> 5) Page can'be reconstructed correctly because of p.1 and p.2
> I think that stateless flag should be precalculated right after initialization step and should be changed due to some stuff in "configuration" methods.
> What do you think?
> Will provide "quick start" in near future!



--
This message was sent by Atlassian JIRA
(v6.2#6252)