On Tue, Feb 8, 2011 at 6:39 PM, Justin Deoliveira <[email protected]> wrote: > While I very much appreciate the work the appschema folks have been doing I > do agree that there is room for a solution that does not involve xml schema > mapping, as your use case and past experiences clearly indicates. > As for going from featureType to xml schema without a predefined schema (for > complex features) I don't know if there is any code that will do this > precisely. But there are bits of code lying around that could be used.. The > code we use for simple features (that currently lives in geoserver) could be > adapted to support the complex feature case. Although I imagine it would > rely on conventions in how the complex feature type structure is built when > determining how to map that to an xml schema. > Doable imo though.
Sounds good. What about the GML encoding of features? Does it require an external schema or can it work off the FeatureType definition? Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ 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
