Hello,
First of all, I am still using GeoServer 2.0.2, so I don't know if this was fixed or changed in 2.0.3 or the 2.1 RCs.
I think there are some Problems in the Rest Api when using it to get Information about Layers with URLs like "geoserver/rest/layers/<l>".
First it does not include workspaces into layernames. So if I use it to get Information about a layer called "workspace:layername", I have to remove the workspace first. This is not a big problem, unless there is another layer with an identical name in another workspace. In that case it will only find one of those layers (in my case the older one).
Another problem are Layers (and probably any other resource) with a space in its name. If I look for a Layer named "layer name", the rest api will reply with "No such layer: layer%20name". It seems the URL encoding is a problem in this case.
I am not sure if anything of is working as intended or if it is a Bug or if I should file a feature Request about this. As I said before I am also not sure if this was fixed in newer version.
Best Regards,
Mirko
Hi Mirko,
You should use the users list for this type of query.
Long story short the first issue is still open and the second has been solved in later versions than 2.0.2.
-Justin
On Thu, Apr 14, 2011 at 2:21 AM, Mirko Bothe <mirko.bothe@anonymised.com> wrote:
Hello,
First of all, I am still using GeoServer 2.0.2, so I don’t know if this
was fixed or changed in 2.0.3 or the 2.1 RCs.
I think there are some Problems in the Rest Api when using it to get
Information about Layers with URLs like “geoserver/rest/layers/”.
First it does not include workspaces into layernames. So if I use it to
get Information about a layer called “workspace:layername”, I have to
remove the workspace first. This is not a big problem, unless there is
another layer with an identical name in another workspace. In that case
it will only find one of those layers (in my case the older one).
Another problem are Layers (and probably any other resource) with a
space in its name. If I look for a Layer named “layer name”, the rest
api will reply with “No such layer: layer%20name”. It seems the URL
encoding is a problem in this case.
I am not sure if anything of is working as intended or if it is a Bug or
if I should file a feature Request about this. As I said before I am
also not sure if this was fixed in newer version.
Best Regards,
Mirko
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation – Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.