[
https://issues.apache.org/jira/browse/WICKET-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467847
]
Eelco Hillenius commented on WICKET-237:
----------------------------------------
Hi Flavius:
You can read about the change and how to build a dynamic component tree here
http://cwiki.apache.org/WICKET/migrate-20.html#Migrate-2.0-Constructorchange
Late binding is something that indeed cannot be done, but this late binding was
exactly what stood in the way of better (more concise and earlier) error
reporting and direct access to markup and parents at construction time.
If you have any questions or want to discuss more, please send a message to the
developer list.
> Constructor change, Component#add
> ---------------------------------
>
> Key: WICKET-237
> URL: https://issues.apache.org/jira/browse/WICKET-237
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 2.0
> Reporter: Flavius Burca
> Assigned To: Johan Compagner
> Priority: Blocker
>
> By removing the Component#add function, the component-based architecture of
> Wicket is compromised.
> A component-based architecture relies on component reuse and with this
> Constructor change you cannot have reusability of components.
> - How could you create a dynamic component hierarchy without a Component#add
> method ?
> - How could you allow later binding of components without a Component#add
> method ?
> - What if you want to reuse a previously created component ?
> - What if you want to create the child component before the parent component
> and link them at a later time ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
