[
https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062681#comment-13062681
]
Juergen Donnerstag commented on WICKET-3335:
--------------------------------------------
@Igor not sure I understand. I thought that for all components (queued or not)
onInitialize gets called in any case after it was added and it's markup is
available. onInitialize will never be called for queued components while still
waiting to be added. During unqueuing the component gets added and because it's
markup is guaranteed to be available, onInitialize gets called. Did I
misunderstand your question?
> 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
> Assignee: Igor Vaynberg
> Fix For: 1.6.0
>
> Attachments: 0001-component-queuing.patch, wicket-3335.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
