[
https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032528#comment-13032528
]
Igor Vaynberg commented on WICKET-3335:
---------------------------------------
there shouldnt be any ambiguities because all containers support queuing.
so if you have two components with the same id and you want to queue them both
you have to queue them under a parent that will not cause ambiguities, eg
lets say you have
c1->input
c1->c2->input
the following code should obviously not work
queue(new Container("c1"));
queue(new Container("c2"));
queue(new Input("input"));
queue(new Input("input"));
because the page does not know how to resolve which input goes where, but - the
following
Container c2;
queue(new Container("c1"));
queue(c2=new Container("c2"));
queue(new Input("input"));
c2.queue(new Input("input"));
should work because we have removed the ambiguity.
> 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
