[
https://issues.apache.org/jira/browse/WICKET-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707543#comment-16707543
]
ASF GitHub Bot commented on WICKET-6608:
----------------------------------------
Github user svenmeier closed the pull request at:
https://github.com/apache/wicket/pull/342
> Stateless page, mix of queue and add can cause unforseen consequences
> ---------------------------------------------------------------------
>
> Key: WICKET-6608
> URL: https://issues.apache.org/jira/browse/WICKET-6608
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.1.0
> Reporter: Oddgeir Bell
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 9.0.0
>
> Attachments: statelessQueueAdd.zip
>
>
> We are in the process of upgrading a Wicket 6.x application to Wicket 8.1,
> mostly because we needed stateless ajax.
> In the process we discovered something quite unexpected (took a few days to
> figure out the cause).
> This is the issue:
> Stateless page.
> Hierarchy like so:
> Page
> ->Container
> ->Label
> ->AjaxButton
>
> The label should only be visible when it's model has data, so we override
> onConfigure and set visible = (getDefaultModelObject != null).
> This works if all components are added with add(Component).
> It also works if all components are added with queue(Component).
> BUT, if the container is added with add(Component) and the AjaxButton is
> added with queue(Component), it doesn't work.
> Actually, if just one component is added to the page with queue(Component),
> things seem to work (as long as it is queue-ed AFTER the container is add-ed)
> I could not find any information on dangers of mixing add/queue with my
> google-fu, so it may look like it's a bug?
>
> Attached quickstart that shows the issue.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
