An interesting response to a question asked on the incubator list
(general@) regarding signing releases. If you are a prospected release
manager, take note!
Martijn
-- Forwarded message --
From: William A. Rowe, Jr. [EMAIL PROTECTED]
Date: Aug 30, 2007 8:47 AM
Subject: [board
Hi,
It (1.3.0-beta3) does complain in if the component isn't added to the page
yet,
but it also complains if the component is null. If I understand this right
(and if the javadoc is correct), it shouldn't complain in the latter case.
cheers,
Jonas
I'm not sure if this was fixed in 1.3, but the
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
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.
