org.geotools.expr
Interface Expr

All Known Subinterfaces:
GeometryExpr, MathExpr
All Known Implementing Classes:
org.geotools.expr.AbstractExpr, AbstractGeometryExpr, AbstractMathExpr

public interface Expr

Filter/Expression construction kit - this class forms chains.

I can't take Filter anymore, the turning point was the fact that I needed a FeatureType to make a AttributeExpression. Simply *no*, I cannot expect customer code to have to jump through hoops so that my impmentation is easier. Late binding is required.

The answer - while not completely forcing DataStores away from Expression/Filter is to make a class that captures all the same information and can do the late binding.

On the way we thre we are not going to have the difference between Filter/Expression. Expr can make an Expression, and Expr can make a Filter.

Example:
Exprs.bbox( extent ).and( Exprs.attribute("cost").lt( 50 ) )

BTW: just so we can have everything make sense

Wild idea time: chaining parameters