First of appologizes to Andrea for the confusion - we are talking about
capturing the idea of DefaultGeometry (not removing it).
In talking with Justin the following idea was brought up, rather then
add a PropertyAccessor method to getDefaultGeometry
we should handle it as yet another PropertyAccessor implementation. That
is one that recognizes requests for xpath="" and target=Geometry.class.
BEFORE
if( expression == null ){
geometry = feature.getDefaultGeometry();
}
else {
geometry = (Geometry) expression.evaulate( feature );
}
AFTER
if( expression == Expression.NULL ){
expression = DEFAULT_GEOMETRY;
}
geometry = DEFAULT_GEOMETRY.evaulate( obj, Geometry.class );
Where the filter would make use of the following static final Expression
DEFAULT_GEOMETRY = ff.property( "" );
And a property accessor would be supplied to handle this case.
Justin I will start modifying these PropertyAccessor implementation to
allow for Geometry.class as a context - and hopefully you can get back
with the sanity check before it is commited.
Cheers,
Jody
-------------------------------------------------------------------------
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
