I can’t seem to find a good description on the geoserver site, does this mean that if you use it geoserver will create an internal featurestore? For the feature server, do you put the credentials in for the geoserver instance to use?
Ryan Moquin ha scritto:
I can't seem to find a good description on the geoserver site, does this mean that if you use it geoserver will create an internal featurestore?
No, it means you'll be able to cascade a remote WFS server, render its
data as maps, generate kml and so on. Whatever you can do with the usual
data sources, you'll be able to do with the data retrieved by the
remote wfs server (usually quite a bit slower thought since the transmission and decoding times are not small).
For the feature server, do you put the credentials in for the geoserver instance to use?
I don't understand this one? 
Cheers
Andrea
Ryan Moquin ha scritto:
If I go to the Geoserver configuration and select data -> datastores. Then I select New and select "Web Feature Server". I can't seem to get any parameters to work for the setup of a "Web Feature Server" datastore. I'm trying to understand what I can do with it. I'm still trying to at the minimum at least find a way to add a datastore to geoserver that I can programmatically update at runtime.... in whatever the easiest way to do this would be... I was trying to do it with a shapefile, but I can't get geotools to save feature information to my shapefile. Even if I got that to work, I'm not sure a shapefile datastore can be updated programmatically with points (such as a setup)..... I'm hoping maybe the wfs datastore would be a solution? I just need a container that is distributable that I can presetup and then initialize with points...
No, the WFS datastore is not what you're looking for.
I'm wondering why the shapefile is not working for you... what exactly
goes wrong? Or else, how are you populating it?
Anyways, there is one that for pure demo purposes and for very limited
amount of data might work: the property datastore.
The property datastore is backed by a simple text file format, can host
basically any data type. Drawbacks are there are no spatial indexes,
and reading is slow, so it's not recommended for anything but very
isolated demos.
The real solution would be the H2 datastore (H2 being a java embeddable
database) but it's still in the works and available only on geoserver
trunk (which is a long way to be released).
Cheers
Andrea