On 8/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> I think what you want can be compared to what Tapestry supports.
the reason this works ok for tapestry is because component hierarchy is very
flat. 99% usecase is you have a page and you add a bunch of components to
it, one level deep. wi
On 8/30/07, akast <[EMAIL PROTECTED]> wrote:
>
> As I'm learning Wicket, it strikes me as redundant that your component
> hierarchy must essentially be expressed twice: once in the Java code, then
> again in your HTML file.
>
> Why doesn't the Java code instead just define an unstructured "pool" of
