Hi,
It is possible to create a data store from WFS by using the Web Feature Server (NG) as a vector data store. Have a try with http://demo.opengeo.org/geoserver/wfs. Because is works it means that Geoserver can parse GetCapabilities from another Geoserver WFS. We need more information about what you doing and what makes you think that the document is malformed.
All you should need is to get valid GetCapabilities and DescribeFeatureType documents as they are defined in WFS standards and I have been cascading WFS successfully from Mapserver, deegree, Geoserver, and TinyOWS.
-Jukka Rahkonen-
Bernardo Marques wrote:
···
Hello everyone,
Recently I’ve been trying to develop a minimal WFS server capable only of “GetCapabilities”, “GetFeature” and “DescribeFeatureType” operations. For that purpose I based my implementation on the WFS simple open source implementation available in JAVA.
The thing is, I got the WFS server up and running and I attempted to get geoserver to use my server as a store. Turns out, the capabilities document was malformed, which was a bit surprising due to its relative simplicity so far. Anyway, I wouldn’t be asking for help and clarification if it wasn’t for the following situation: I then proceeded to get geoserver’s capabilities document itself, and served it to geoserver himself. However, it turned out to be a malformed document also.
So, my question is: Are there any guidelines on how to write a capabilities document that geoserver can parse?
thanks