[Geotools-devel] Too many places are still not working with geoapi filters

[Andrea A. <aa...@op...>]

Hi all,
a little rant for trunk... there is still a ton of places that simply
require old filters, cast to them, and makes life impossible for
people trying to use the new filters.

Do you think I'm asking for too much when I say we should get rid
of all usages of filters before releasing 2.4.0M0?
We already released the 2.3.x basically screwed filter wise,
do we want to repeat that with 2.4.0?

In particular, my crash is due to the 
PostPreProcessFilterSplittingVisitor, used by all JDBC data stores
to perform filter splitting. As a result of transformations, my filters 
do contain Filter.EXCLUDE, and the filter splitter just breaks with a
class cast exception when it encounters them.

With other filters the issue is not apparent, because despite 
interfaces, all filters are still implementing the old Geotools 
interfaces. All, but not Filter.INCLUDE, Filter.EXCLUDE.

Cheers
A frustrated Andrea