[
https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053299#comment-13053299
]
Igor Vaynberg commented on WICKET-3335:
---------------------------------------
its not exactly how it works. queue(new Container("c1")) will not be
immediately executed, none of them will. unqueueing happens after/before? the
initialization of the component when the markup is available.
when dequeuing we try to find a queued child closest to the container, so in
the example above it will work like this:
resolving c1, found and dequeued
resolving c1->input. look in c1, not found. look in parent, found and dequeued
resolving c2. look in c1, not found. look in parent, found and dequeued
resolving c2->input: look in c2, found and dequeued
also i now think queue is too cumberson to type, we should probably rename it
to "push"
> 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
