Fair enough. My point was that having the schema around implies that the filter can only be executed against features of a particular type. For instance.
Currently: FeatureType type1 = ...; Feature f1 = type1.create( ... ); AttributeExpression e1 = factory.attribteExpression( type1, "foo" ); Attribute a = e.evaluate( f1 ); FeatureType type2 = ...; Feature f2 = type.create( ... ); AttributeExpression e2 = factory.attribteExpression( type2, "foo" ); Attribute a = e2.evalute( f2 ); Alternative: FeatureType type1 = ...; FeatureType type2 - ...; AttributeExpression e = factory.attribteExpression( "foo" ); Attribute a1 = e.evaluate( f1 ); Attribute a2 = e.evaluate( f2 ); But by all means, add the getter. -Justin Andrea Aime wrote: > Justin Deoliveira ha scritto: >> The implementation of AttributeExpression allows for features of differnt >> types or shchemas. Having this method assumes only one. It would be nice >> if the two were consistent. > > I'm not sure I understand. The implementation references a single schema > object, > which may be null. I just want to expose it thru a getter... confused... > > Cheers > Andrea > > !DSPAM:1004,4514e63a131261362196140! > -- Justin Deoliveira [EMAIL PROTECTED] The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
