On Thu, Aug 30, 2012 at 4:35 AM, <[email protected]> wrote:
> Hi Andrea, others,
>
> I've gathered up all your recent questions to answer them all together,
> the last one also pertains to your question about creating complex feature
> types from an XSD:
>
> Q: Is the WFS data store going to return back simple features and simple
> feature types for simple feature GML?
> A: I haven't changed the semantics of WFSDataStore or WFSContentDataStore
> so they still work exclusively with simple types. I added
> WFSContentDataAccess which I have made to interact with complex types only.
> Do you think their functionality should be combined?
>
That's an interesting question. What if a certain WFS server is serving a
mix of simple and complex types?
Put in other terms, it would be useful if WFSContentDataAccess could serve
also simple features on occasion, but I'm not going to hold
the commit on this.
On the other side, it would be good if Gabriel had a look at the changes,
since he's currently active on the WFS store
>
> Q: Looking at the code it seems you are coming from C# sometimes, I see
> methods starting with a capital here that should be fixed:
>
> https://github.com/Adam-Brown/geotools/blob/master/modules/unsupported/wfs-ng/src/main/java/org/geotools/data/wfs/internal/parsers/XmlComplexFeatureParser.java
> e.g. private void RegisterGmlTarget(String id, Attribute value) { ...
> A: Ha, old habits die hard! I did come from a C# background :) I have
> updated those method names to use initial lowercase. I looked through the
> other files I've been working on and didn't see any similar mistakes but I
> apologise in advance if I've missed any.
>
No problem
>
> Q: Btw, looked around a bit but I haven't seen a
> "ComplexFeatureTypeBuilder". Is there anything like that?
> A: I discussed this with Ben who recommended I use the app schema resolver
> to get the types. This is happening in the
> WFSContentDataAccess.getSchemaParser() method.
>
Ah. Is there any chance the app schema resolver can be pushed in a more
centralized position?
While I understand it's handy to reuse it as it, it has the side effect of
having the WFS depend on app-schema.
It's as if the shapefile datastore depended on the Oracle one, if you get
what I mean.
This would also have the side effect of bringing the app-schema store
straight into core in GeoServer land,
something for which it's clearly not ready lacking a UI for its
configuration
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
