Andrea, there is no support for converting complex FeatureTypes into schemas. app-schema delivers schemas by returning a document that includes or imports the application schemas from their canonical location.
The GML encoding requires a schema document to feed into EMF to configure the encoder. The EMF-parsed schema is smuggled via UserData on the FeatureType into the encoder. The encoder needs to know about things like substitution groups that do not exist in the GeoAPI model. Regards, Ben. On 09/02/11 01:27, Andrea Aime wrote: > Hi, > I'm asking to satisfy a curiosity. I know that complex feature people > are all about > interoperability with application schemas and the like, but only the > cases demanding > complex features I keep on stumbling on do not use/require published > app schemas at all... > > I'm wondering, assuming I can make a data store that builds and > describes complex > features out of some native structure (might be javabeans for example) how > would > the rest of the code react? > > In particular, is there any support to encode a FeatureType into an XML schema > like we do for simple features? > And would the gml encoding for features work without having a published schema > to target? > > Cheers > Andrea > -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
