Description
Came across this bug when upgrading from wicket 1.3 to 1.4.7. It occurred when we were clearing a form.
Add a null check to
selectedValues.addAll(getConvertedInput());
in ListMultipChoice:updateModel(),
because getConvertedInput() can conceivably be null in normal situations.