[WICKET-5225] Inconsistent behaviour of org.apache.wicket.Page.isPageStateless()

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.8.0
• Fix Version/s: 6.9.0, 7.0.0-M1
• Component/s: wicket-auth-roles
• Environment: any
• Assignee: Unassigned
• Reporter: Mischa Neumann
• Created: 11/Jun/13 21:14
• Updated: 29/Oct/13 13:21
• Resolved: 29/Oct/13 13:21

Description

we have a page with

• a login form A (org.apache.wicket.markup.html.form.StatelessForm<T>)
• a standard form B inside a panel which is secured with @AuthorizeAction(action = Action.RENDER...)

our problem: the user must submit the login form twice.

reason:

• when the page is requested the first time, the page is stateless cause none of the visible children are stateful.
• when the user now submits the login form, the page claims to be stateful, the stateful component is form B.
• org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(IRequestCycle) now handles the page as expired and omits the submit

possible buggy code:

• the visiblity of components is computed before rendering in org.apache.wicket.Component.setRenderAllowed()
• org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(IRequestCycle) calls only org.apache.wicket.MarkupContainer.internalInitialize() on the current page to give it a chance for computing its visibility, Component.setRenderAllowed() is not called