[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030386#comment-13030386 ]
Juergen Donnerstag commented on WICKET-3335: -------------------------------------------- Another way to solve it (we actually had that in 1.2 or so) is to extend/replace the component resolution process. > 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