[jira] [Updated] (WICKET-5732) Improve component queuing and auto component

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

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

Andrea Del Bene updated WICKET-5732:
------------------------------------
    Affects Version/s: 7.0.0-M3

> Improve component queuing and auto component
> --------------------------------------------
>
>                 Key: WICKET-5732
>                 URL: https://issues.apache.org/jira/browse/WICKET-5732
>             Project: Wicket
>          Issue Type: Task
>    Affects Versions: 7.0.0-M3
>            Reporter: Andrea Del Bene
>            Assignee: Andrea Del Bene
>            Priority: Critical
>
> One of the new feature implemented in Wicket 7 is component queuing (see https://www.42lines.net/2014/02/28/component-queueing-in-wicket-7).
> Amongst other things, component queuing is aimed to improve auto components usage.
> The current implementation of component queuing has raised some issues (WICKET-5730, WICKET-5724) which might make impossible for a Wicket application to migrate from 6.x to 7.x.
> As a consequence I've tried to find a solution that could solved the encountered issues without changing the expected behavior for component queuing. The solution can be seen in the new branch 'improvingQueuing' (https://github.com/apache/wicket/tree/improvingQueuing).
> However, this solution comes at the price of changing the current way Wicket handles auto component. So far Wicket removes auto components added during rendering phase after this latter has finished. On the contrary, my solution implies that auto components must stay in their hierarchy
> This is of course quite a big change to Wicket internals, so ad Martin Grigorov suggested, we should discuss it before merging it to master branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)