Justin, I am running into severe problems writing generic support for encoding of application schema WFS responses. I must have support for XML attributes and for new complex types defined in schemas. ComplexBinding has getProperty and getProperties methods:
(1) getProperty returns a single property by name (2) getProperties returns all the properties, determined from the children of the XSD element declaration I need both because I need to support XML attributes (stored as GeoAPI Attributes) and these are accessed with (1) via AttributeEncodeExecutor, but, for application schemas, encoding is driven by XSD declarations using (2) via ElementEncodeExecutor, which also uses (1). It looks like these *must* return disjoint sets of properties, or I get duplicate encoding of elements. Is this expected? Orchestrating these methods is hard because getProperty goes not have access to the XSDElementDeclaration. It cannot set an XSDParticle for returned objects, yet how can it know which properties to leave for getProperties without knowing the XSDElementDeclaration? Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ 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
