Hey, working with app-schema on trunk (and thrilled by the feature-chaining stuff), I fount that when it comes to gml encoding, lots of warnings are thrown by GetPropertyExecutor.visit (line 74), because the binding.getType does not match the Attribute's type.
For instance, the binding FeaturePropertyTypeBinding.getType() returns Feature.class, when it seems it shouldn't, and instead it should return ComplexAttribute.class? The thing is, the binding for Feature is AbstractFeatureTypeBinding, and in a schema, a type deriving from gml:FeaturePropertyType is meant to reference a Feature, not to be a Feature.. I may be missing something and that's like that thinking in the same way than, say, PointPropertyType. But that's a different case because geometry types are special in the sense that the gml:propertyType element for them is created because JTS Geometry instance _are_ allowed to be direct childs of a ComplexAttribute... (I'm screwing it but you surely got why geometries are a special case) In any case, for nested features where the gml:propertyType pattern is either followed or not by the scheme explicitly, I think FeaturePropertyTypeBinding should not be tied to Feature.class. Comments? -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
