In a project we extend DefaultItemSorter. Its not a big thing but we would require much less copy & paste if the properties in DefaultItemSorter were protected instead of private. Or is it not intended to extend the DefaultItemSorter?
Cheers,
Rene
There should not be any reason not to extend the DefaultItemSorter class. Unfortunately, for now, you have to copy paste the code. I cannot say when and if it will change, though I pray it will soon(ish).
I would say most cases can be handled simply by using DefaultItemSorter(Comparator), and the really complicated cases could benefit from a completely customized ItemSorter.
Given those options, making all fields protected might open it up (and restrict future changes) a bit too much compared to the benefits, but protected getters for the fields and using them in the internal methods would probably be a good idea to enable some more customization. Could you
create an enhancement request
about this (including also a link to this thread)?