in the last few days I played a bit with GeoServer 2.0-RC1 and find several issues.
I’m going to list them here since actually I don’t know if are known issues or they need a specific JIRA, I will wait for feedbacks on this.
It’s not possible to update the WMS metadata configuration at all form the UI cause of a wired error saying “The following codes are not known to the EPSG authority: ” … the error disappears if I put at least one SRS ID on the Limited SRS list textbox
The WFS-T does not work anymore using a client like uDig while it seems to work fine issueing the requests directly
Though it’s possible to modify a Style of one of the layers on a layergroup by unchecking it, once the layer is re-enabled again the default style is grabbed back again
The WMS GetFeatureInfo templates seem to not work anymore, or at least to update them anymore.
in the last few days I played a bit with GeoServer 2.0-RC1 and find several issues.
Many issues have been found already and fixed, it's advisable to test
a nightly instead or RC1
I'm going to list them here since actually I don't know if are known issues or they need a specific JIRA, I will wait for feedbacks on this.
1. It's not possible to update the WMS metadata configuration at all form the UI cause of a wired error saying "The following codes are not known to the EPSG authority: " ... the error disappears if I put at least one SRS ID on the Limited SRS list textbox
Already fixed
2. The WFS-T does not work anymore using a client like uDig while it seems to work fine issueing the requests directly
This is new, which version of uDig?
3. Though it's possible to modify a Style of one of the layers on a layergroup by unchecking it, once the layer is re-enabled again the default style is grabbed back again
Can you first check with a nightly and then provide a step by step
report if the issue persists? For example it's not clear what you
mean by "layer re-enabled again".
4. The WMS GetFeatureInfo templates seem to not work anymore, or at least to update them anymore.
The templates have to be placed in a different folder now as far
as I know, that is, in the folder that contains the layer configuration.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
in the last few days I played a bit with GeoServer 2.0-RC1 and find several issues.
Many issues have been found already and fixed, it's advisable to test
a nightly instead or RC1
I'm going to list them here since actually I don't know if are known issues or they need a specific JIRA, I will wait for feedbacks on this.
1. It's not possible to update the WMS metadata configuration at all form the UI cause of a wired error saying "The following codes are not known to the EPSG authority: " ... the error disappears if I put at least one SRS ID on the Limited SRS list textbox
Already fixed
2. The WFS-T does not work anymore using a client like uDig while it seems to work fine issueing the requests directly
This is new, which version of uDig?
WFS-T for udig is only available for WFS 1.0.0, though read-only support exists for 1.1.0. Try setting the VERSION=1.0.0 parameter to the GetCapabilities URL and it _should_ work just as before.
Hope that helps,
Gabriel
3. Though it's possible to modify a Style of one of the layers on a layergroup by unchecking it, once the layer is re-enabled again the default style is grabbed back again
Can you first check with a nightly and then provide a step by step
report if the issue persists? For example it's not clear what you
mean by "layer re-enabled again".
4. The WMS GetFeatureInfo templates seem to not work anymore, or at least to update them anymore.
The templates have to be placed in a different folder now as far
as I know, that is, in the folder that contains the layer configuration.
Cheers
Andrea
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
in the last few days I played a bit with GeoServer 2.0-RC1 and find several issues.
Many issues have been found already and fixed, it's advisable to test
a nightly instead or RC1
I'm going to list them here since actually I don't know if are known issues or they need a specific JIRA, I will wait for feedbacks on this.
1. It's not possible to update the WMS metadata configuration at all form the UI cause of a wired error saying "The following codes are not known to the EPSG authority: " ... the error disappears if I put at least one SRS ID on the Limited SRS list textbox
Already fixed
2. The WFS-T does not work anymore using a client like uDig while it seems to work fine issueing the requests directly
This is new, which version of uDig?
WFS-T for udig is only available for WFS 1.0.0, though read-only support exists for 1.1.0. Try setting the VERSION=1.0.0 parameter to the GetCapabilities URL and it _should_ work just as before.
Gabriel, I was thinking... since udig wfs is fully capable only in v 1.0.0, shouldn't it try to negotiate the usage of 1.0 and fall back
on 1.1 only as a last resort?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
in the last few days I played a bit with GeoServer 2.0-RC1 and find several issues.
Many issues have been found already and fixed, it's advisable to test
a nightly instead or RC1
I'm going to list them here since actually I don't know if are known issues or they need a specific JIRA, I will wait for feedbacks on this.
1. It's not possible to update the WMS metadata configuration at all form the UI cause of a wired error saying "The following codes are not known to the EPSG authority: " ... the error disappears if I put at least one SRS ID on the Limited SRS list textbox
Already fixed
2. The WFS-T does not work anymore using a client like uDig while it seems to work fine issueing the requests directly
This is new, which version of uDig?
WFS-T for udig is only available for WFS 1.0.0, though read-only support exists for 1.1.0. Try setting the VERSION=1.0.0 parameter to the GetCapabilities URL and it _should_ work just as before.
Gabriel, I was thinking... since udig wfs is fully capable only in v 1.0.0, shouldn't it try to negotiate the usage of 1.0 and fall back
on 1.1 only as a last resort?
I guess so, would need to check what's the actual state of it right now on udig... it used to be like that but I'm not completely sure right now.. gonna check
Cheers
Andrea
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
2. The WFS-T does not work anymore using a client like uDig while it
seems to work fine issueing the requests directly
This is new, which version of uDig?
WFS-T for udig is only available for WFS 1.0.0, though read-only support
exists for 1.1.0. Try setting the VERSION=1.0.0 parameter to the
GetCapabilities URL and it _should_ work just as before.
Gabriel, I was thinking... since udig wfs is fully capable only in v
1.0.0, shouldn't it try to negotiate the usage of 1.0 and fall back
on 1.1 only as a last resort?
It negotiates back of the version number is not specified; if the
version number is specified it tries to play along.
