[Geoserver-users] WFS as datastore

Hi to all,
I am using GeoServer for managing geo-data. I am able to set and query WFS
and WMS with Postgis and shapefile data but I can't set up a new WFS
datastore.

I didn't find any tutorial and I don't know how to fill the
"WFSDataStoreFactory:GET_CAPABILITIES_URL" field.

I put in it the url of the GetCapabilities request (as I have understood
from the field's name) but GeoServer says that "Could not find
file....Perhaps location was entered wrong?".

Why GeoServer is searching for a FILE???

I think that I have done all wrong.

Any suggestions?

Thanks a lot

Anna Zanetti
--
View this message in context: http://www.nabble.com/WFS-as-datastore-tf3945274.html#a11191465
Sent from the GeoServer - User mailing list archive at Nabble.com.

Anna Zanetti ha scritto:

Hi to all,
I am using GeoServer for managing geo-data. I am able to set and query WFS
and WMS with Postgis and shapefile data but I can't set up a new WFS
datastore.

I didn't find any tutorial and I don't know how to fill the
"WFSDataStoreFactory:GET_CAPABILITIES_URL" field.

I put in it the url of the GetCapabilities request (as I have understood
from the field's name) but GeoServer says that "Could not find
file....Perhaps location was entered wrong?".

Why GeoServer is searching for a FILE???

I think that I have done all wrong.

Well it's not really you. Which version of Geoserver are you using?

We did try out the WFS datastore as a way to support cascading WFS,
but it wasn't working properly, and we just gave up due to lack of time.
For what I remember, we were unable to properly cascade another geoserver, or for that matter, any server that uses namespace:layer
format for the layer name. What WFS are you trying to cascade?

Oh, I noticed just now that WFS is still included
as one of the extension datastores, sigh..

As for you specific error, I believe that you're getting stuck because
of a check we added lately. Basically, we were fed up of noticing
shapefiles were badly configured (wrong path) only when trying to
setup the feature type, so we added a generic check for URL existance
on the file system... that is because both raster data and shapefiles use URL as the parameter that holds the "on the file system" path.

That's obviously not working in your case, where the URL is a real internet URL for a change. Anna, can you open a jira issue so that
we don't forget about this, and we can remove at least this roadblock
before releasing 1.5.2?

Ciao
Andrea

Andrea Aime ha scritto:

That's obviously not working in your case, where the URL is a real internet URL for a change. Anna, can you open a jira issue so that
we don't forget about this, and we can remove at least this roadblock
before releasing 1.5.2?

Oh well, I opened it myself:
http://jira.codehaus.org/browse/GEOS-1164

Cheers
Andrea

Good morning,

sorry but I didn’t know how to open a ’ jira issue '. And I had not the possibility to tell you this before.

Thanks a lot

Best regards.

Anna Zanetti

Anna Zanetti ha scritto:

Good morning,

sorry but I didn't know how to open a ' jira issue '. And I had not the possibility to tell you this before.

No problem. We have a little guide on how to report issues, I should have pointed you to it earlier:
http://docs.codehaus.org/display/GEOSDOC/1+Reporting+Issues

If you want to be informed when the bug will be fixed, I suggest
you register as a Jira user, log in, then go to
http://jira.codehaus.org/browse/GEOS-1164 and become a watcher
of the issue.

Cheers
Andrea