Justin Deoliveira wrote: > Ideally everything is handed by bindings, and there is only a > BindingPropertyExtractor. My advise to you is to have everything handled > by a special AbstractFeatureTypeBinding for complex content.
(1) How do I register a second binding for GML.AbstractFeatureType when one already exists? If I do this, many unit tests break. (2) If I can have multiple bindings for the same GML type, would you expect them to be applied in any predictable order? (3) How do I write a binding for GML types whose name is not known at compile time? In my earlier example GeologicFeaturePropertyType is a complex type defined in an application schema. 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 ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
