Can you produce a test case so we can see what you are seeing? Does it matter which data source you use or is this strictly a problem with SimpleFeatureImpl?
I did think that SimpleFeatureImpl was only allowed one geometry and I am not sure anyone tested doing anything other then setting the default geometry. Jody On 19/05/2010, at 7:53 PM, Thorsten Reitz wrote: > Hi all, > > I have identified a strange behaviour when setting the value of a property: > > I retrieve and set the property as follows: > feature.getProperty(propertyname).setValue(new_geometry); > > feature is a SimpleFeatureImpl, with a SimpleFeatureType that has among > others a geometry property identified by propertyname, new_geometry a > JTS Point Geomentry. > > Stepping through the debugger, everything looks OK - in the end, > setValue() of PropertyImpl is invoked. However, after this procedure, > the feature's property doesn't have any value assigned to it. > > To make things even stranger, this doesn't happen always, it seems that > only geometric attributes are affected. > > I should add that when using FeatureImpl instead of SimpleFeatureImpl, > setting the value also works. > > Any ideas what this issue might be? N.b. that I am using GT 2.5.8. > > Thanks & kind regards, > > Thorsten > > -- > Thorsten Reitz > > Fraunhofer-Institut für Graphische Datenverarbeitung IGD > Fraunhoferstr. 5 | 64283 Darmstadt | Germany > Tel +49 6151 155-416 | Fax +49 6151 155-444 > [email protected] | www.igd.fraunhofer.de > > ------------------------------------------------------------------------------ > > _______________________________________________ > Geotools-gt2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users ------------------------------------------------------------------------------ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
