[
https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053284#comment-13053284
]
Juergen Donnerstag commented on WICKET-3335:
--------------------------------------------
What shall be the resolution logic in the example below
c1->input
c1->c2->input
Container c2;
queue(new Container("c1"));
queue(c2=new Container("c2"));
queue(new Input("input"));
c2.queue(new Input("input"));
I assume:
queue(new Container("c1")); will immediately be executed because we don't need
to wait for anything
queue(c2=new Container("c2")); same; invoke add() immediately
queue(new Input("input")); can be added to c1 or c2. Shall that request be
stalled until later? Until when? Or shall it be added to the first occassion it
finds (without a warning)?
c2.queue(new Input("input")); can be executed immediately without ambiguity.
Should we retry the postponed entry now? In that case queue can only do add but
no replace (IMO not a heavy limitation).
> Component Queuing (extract hierarchy information from markup)
> -------------------------------------------------------------
>
> Key: WICKET-3335
> URL: https://issues.apache.org/jira/browse/WICKET-3335
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-core
> Reporter: Giannis Koutsoubos
> Attachments: 0001-component-queuing.patch
>
>
> Doubly defined hierarhices are redundant.
> Server-side hierarchy can be automatically deduced from markup hierarchy.
> Use queue method in MarkupContainer to add components and extract hierarchy
> information from markup.
> Discussed here:
> http://apache-wicket.1842946.n4.nabble.com/Free-wicket-from-component-hierarchy-hell-td3027705.html
> Implementation of queue method on branch 1.4.x :
> https://github.com/koutsoub/wicket/tree/component-queuing
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
