for now i accept eelco's hack only because i think it is a necessity at this point in time.
Exactly. Imo, we need something like FormComponentPanel in 1.3/ 2.0 sooner rather than later. In the past I've had a couple of times where I just spent too much time trying to work in other ways, while this panel really is easy (and elegant enough) to use. Whether it is a hack or not is debatable. It is a workaround for sure, but at the same time, it fulfills a specific function no other components do: an aggregate of (form) components that can interact with the form processing but that doesn't receive user input itself. Imo, in the current state of Wicket, this is not a dirty hack. But in future versions, it would be great if you could achieve the same through mixing in rather than extending. Eelco
