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.
2c.
On Tue, Feb 8, 2011 at 10:27 AM, Andrea Aime
<[email protected]>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
>
> --
> -------------------------------------------------------
> 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
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
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
