[Geoserver-users] capabilities document parsing

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

Yep, i was just able to do it using an example from the WFS standard document. What I was doing was simply serving geoserver’s capabilities document as the capabilities document of an external server. It would then generate a vague parsing exception.

On Oct 22, 2015 08:20, “Rahkonen Jukka (MML)” <jukka.rahkonen@anonymised.com6847…> wrote:

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

On Thu, Oct 22, 2015 at 9:32 AM, Bernardo Marques <
bernardomarques5@anonymised.com> wrote:

Yep, i was just able to do it using an example from the WFS standard
document. What I was doing was simply serving geoserver's capabilities
document as the capabilities document of an external server. It would then
generate a vague parsing exception.

Let's make it less vague then? Share the full stack trace.
It may well be a parsing issue since the caps document has backlinks to
GeoServer itself.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------