[Back on the list] Unit test. It is the only way to be sure.
Kind regards, Ben. On 09/02/11 15:42, Andrea Aime wrote: > On Wed, Feb 9, 2011 at 4:14 AM, Ben Caradoc-Davies > <[email protected]> wrote: >> I was thinking about non-feature polymorphic complex properties. For >> example, CGI_Value and similar types from GeoSciML 2.0: >> http://www.geosciml.org/geosciml/2.0/xsd/value.xsd >> >> The GML striping rule requires that the type (XSD element) is encoded before >> each property name. BindingPropertyExtractor.properties searches the >> substitution group to find all the valid type names, to find the properties >> (this is the GML PropertyType pattern). >> >> This is the first example I can think of where automatically built feature >> types will not be able to support polymorphism. But then, you don't need to >> have polymorphism to be complex! >> >> Andrea, do you have any polymorphic property types in your use case? If not, >> encoding becomes a great deal simpler and will likely work with Java-only >> types. > > Nope, the case I'm looking into is the simplest complex feature ever, it's > just > a main complex feature with a property which is another feature collection > with a known content type > > Cheers > Andrea > -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
