Multiple KVP parsers for the same key will step on each other toes
------------------------------------------------------------------
Key: GEOS-1719
URL: http://jira.codehaus.org/browse/GEOS-1719
Project: GeoServer
Issue Type: Bug
Components: Global
Reporter: Andrea Aime
Assignee: Justin Deoliveira
Priority: Critical
Fix For: 1.7.0-beta1
Trunk has two kvp parsers for acceptVersions parameter that need to output two different objects. The current framework does not have any way to discriminate them and pick the right one.
For the moment I'll be rolling out my custom override code in wcs 1.1.1 to keep things running, but that's not a clean solution
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.codehaus.org/browse/GEOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Aime reopened GEOS-1719:
-------------------------------
Actually, no, it's not solved. Binding to a request is not enough... and I'm not sure how to deal with the problem.
The issue comes with AcceptVersions capabilities request parameter. There are two, one now is in WCS, but I need it for WPS as well, the other is in WFS.
It's basically OWS 1.0 vs OWS 1.1, both define acceptVersions, but for WCS 1.1 and WPS 1.0 we need the OWS 1.1 one, for WFS the 1.0 one is used instead.
And capabilities request does not have a version number... shall we add a service dependency?
Multiple KVP parsers for the same key will step on each other toes
------------------------------------------------------------------
Key: GEOS-1719
URL: http://jira.codehaus.org/browse/GEOS-1719
Project: GeoServer
Issue Type: Bug
Components: Global
Reporter: Andrea Aime
Assignee: Justin Deoliveira
Priority: Critical
Fix For: 1.7.0-beta2
Trunk has two kvp parsers for acceptVersions parameter that need to output two different objects. The current framework does not have any way to discriminate them and pick the right one.
For the moment I'll be rolling out my custom override code in wcs 1.1.1 to keep things running, but that's not a clean solution
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira