Github user duesenklipper commented on the issue:
https://github.com/apache/wicket/pull/292
That is a possibility, yes, though in your example you do hold on to the
connectedCheckBoxes. My main idea was to keep it simple, by providing
addCheckBox() users can just add checkboxes in a loop, e.g. in
ListView#populateItem.
Any checkboxes that are removed from the component hierarchy are cleared
from connectedCheckBoxes by the attached behavior, so there shouldn't be a leak.
But I'm not heavily invested in this design, if you prefer a lookup method,
I can do that.
---
