Confused I am not :)
Let me give you three examples...
I. filtering with a subset of properties
This is a class that worked perfectly in 1.4.19:
public class CustomersDataProvider extends
HibernateDataProvider implements
IFilterStateLocator {
@SuppressWarnings("unused")
public static cl
I think you're confused.
If you want to filter a collection based on type T, then your filter your
extend T.
The idea here is that your model object type for the filter is the same as
that retrieved by the data provider.
As such you can have a POJO of the same type T on which you apply the
filteri
I started migrating my code from wicket 1.4.19 to 6. Finally ! :)
I found a FilterToolbar bug:
Once you were able to create DataTable wrapped inside of
FilterForm
currently FilterToolbar requires you for those two types to be identical:
public FilterToolbar(final DataTable table, final
FilterF
