Add proper support for UPDATESEQUENCE
Description
Environment
Attachments
Activity
codehaus April 10, 2015 at 4:27 PM
CodeHaus Comment From: aaime - Time: Mon, 3 Nov 2008 01:51:11 -0600
---------------------
<p>All these issues have been in "resolved" state for at least one month (many of them, much more than that). Since no one has reopened them, I'm mass-switching them to closed state. Reopen if you feel the issue has not been addressed properly.</p>
codehaus April 10, 2015 at 4:27 PM
CodeHaus Comment From: cholmes - Time: Thu, 14 Feb 2008 14:22:50 -0600
---------------------
<p>Ok, awesome. May have been before our hudson was hooked up with comments - now you just need to include the issue number in the commit message and it'll make a comment here when it builds successfully with it. </p>
codehaus April 10, 2015 at 4:27 PM
CodeHaus Comment From: saul.farber - Time: Thu, 14 Feb 2008 14:11:27 -0600
---------------------
<p>Chris: patch is already comitted on trunk. Somehow I forgot to mark that on this JIRA issue. I'll update this JIRA right now.</p>
codehaus April 10, 2015 at 4:27 PM
CodeHaus Comment From: cholmes - Time: Thu, 14 Feb 2008 14:06:16 -0600
---------------------
<p>You want to open a new jira for 1.7.x? So that this gets tracked on there. You said that it needs review, it'd be good to have it there with the patch and the request for review. </p>
codehaus April 10, 2015 at 4:27 PM
CodeHaus Comment From: jdeolive - Time: Thu, 14 Feb 2008 13:55:15 -0600
---------------------
<p>Integrated in geoserver-1.6.x #49 (See <a href="http://gridlock.openplans.org:8080/hudson/job/geoserver-1.6.x/49/" class="external-link" rel="nofollow">http://gridlock.openplans.org:8080/hudson/job/geoserver-1.6.x/49/</a>)</p>
Details
Details
Assignee
Reporter
Fix versions
Affects versions
Priority
Low
We should consider supporting the update sequence parameter. This may be beyond the scope of what we want to hit immediately, but it could be nice to implement it based on 'saves' done in the admin tool. Of course that would require caching past version somewhere, which could get a bit tiresome. But to fully pass the ACE-GIS tests we should handle this:
test 3
task 1: When a GetCapabilities request is made with an UPDATESEQUENCE parameter set to the current update sequence value, then the server returns a valid exception (code = CurrentUpdateSequence).
task 2: When a GetCapabilities request is made with an UPDATESEQUENCE parameter set to a value higher than the current update sequence value, then the server returns a valid exception (code = InvalidUpdateSequence).
task 3: When a GetCapabilities request is made with an UPDATESEQUENCE parameter set to a value lower than the current update sequence value, then the server returns the capabilities file.