Hello!
I have faced the challenge of having a Feature implementation that is attribute-"nillable" safe. Means if AttributeType is not nillable, we can not create DefaultFeature with null attribute values. There are lot of places where Feature instance must be created with nulls but filled with non-null values (like geometry) later on (templating). Now it is implied to deal with helper objects collecting attribute values and creating Feature instance in the end. DataUtilities.template() methods are failed if attribute types are not nillable but can not create default value. If geometry attribute type is not nillable, it is not obvious about default geometry. Here is a problem with two sides: having safe Feature instance against its FeatureType and having handy Feature template for filling by attributes later. Does GT have the second variant implemented? Vitali. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
