[
https://issues.apache.org/jira/browse/WICKET-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172319#comment-14172319
]
Martin Grigorov commented on WICKET-5724:
-----------------------------------------
It is not very clear to me :-/
Why "auto components are queued if our component queue is not empty" ?
What happens if "our component queue is empty" ?
I've noticed a new method called "innerQueue". Usually such methods are named
"internalXyz". And usually it is "private".
Why the auto components are not removed anymore at the end of the rendering ?
They are in their correct position only when queue() is used. But if add() is
used then they are still auto and should be removed, IMO.
> Queueing component in autocomponent
> -----------------------------------
>
> Key: WICKET-5724
> URL: https://issues.apache.org/jira/browse/WICKET-5724
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0-M3
> Reporter: Palancher aurélien
> Assignee: Andrea Del Bene
> Fix For: 7.0.0-M4
>
> Attachments: queueing-problem.zip, queueing-solution.zip,
> wicket5724.patch
>
>
> There is an exception when a component is added to queue when its parent is
> an auto component
> <body>
> <a href="panier.html">
> <span wicket:id="inlink"></span>
> </a>
> </body>
> Last cause: Unable to find component with id 'inlink' in
> [TransparentWebMarkupContainer [Component id = wicket_relative_path_prefix_1]]
> Expected: 'wicket_relative_path_prefix_1:inlink'.
> Found with similar names: ''
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
