Hmmm.... breakfast. We already allow nested forms, but we don't do
anything about it, and these fail horribly at the moment as Korbinian
reminds us of constantly. The only other option would be to check the
markup and throw a runtime exception that nesting is not allowed.
I think the way we treat nested forms in 2.0 and 1.3 a real
improvement and a showcase for component frameworks: work around
problems in an elegant and meaningful way. Abstract away the
limitations of the protocols we have to work with.
Yeah, I can see that, and the fact that you and Igor think it is
really useful is enough for me to vote +1, but I wrote a lot of Wicket
myself over last two years, and never had to use the construction or
even found it would have solved any problem better. Anyway, enough of
that, you gave a convincing example earlier.
Eelco
