Hello,
I made an innocent programming error that day by adding a Form as a child
component of a TextField thats already the child of the Form. In that case,
execution gets stuck in an infinite loop in Component.findParent(final Class
c). I still am only scratching the surface of wicket, but are
Yeah agreed. I was just wondering if a sanity check is needed at that point
in the code.
Thanks.
On 6/11/07, Alex Objelean [EMAIL PROTECTED] wrote:
You just have to respect the hierarchy you have defined in the markup.
Nart Seine wrote:
Hello,
I made an innocent programming error
Hello, I've been following the discussions here, and this one caught my eye.
Does this mean that Wicket is ill suited for example for creating dynamic
forms that are built dynamically at runtime after reading some page
definition file from xml or some other data store. I havent looked into
Wicket