Opened 17 years ago
Closed 16 years ago
#2312 closed defect (fixed)
WMS GetCapabilities w/Nested Groups
Reported by: | jimk | Owned by: | dmorissette |
---|---|---|---|
Priority: | normal | Milestone: | 5.0.1 release |
Component: | WMS Server | Version: | 5.0 |
Severity: | normal | Keywords: | |
Cc: |
Description (last modified by )
It looks like the previous seg-fault has been fixed but it looks like the fix introduced another bug. The problem is the </layer> tags are closing late in the getCapabilities request. The following patch against r6849 fixes it for me.
Index: mapwms.c =================================================================== --- mapwms.c (revision 6849) +++ mapwms.c (working copy) @@ -1423,7 +1423,7 @@ return MS_FALSE; } /* compare all groups below the current level */ - for (i = 0; i < currentLevel; i++) + for (i = 0; i <= currentLevel; i++) { if (strncmp(currentGroups[i], otherGroups[i], strlen(currentGroups[i])) != 0) {
Attachments (1)
Change History (7)
comment:1 by , 17 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
comment:2 by , 17 years ago
Milestone: | → 5.0.1 release |
---|---|
Version: | unspecified → 5.0 |
Would you have a sample mapfile to use to reproduce and test this? No need for data, I just need the mapfile to run a getcapabilites on it.
comment:3 by , 17 years ago
Notice in the sample mapfile the layer names also follow the hierarchy. So L.2.x should not be grouped under the L.1.x layers.
comment:4 by , 17 years ago
Thanks! I have verified that your proposed change solves the issue with your mapfile and also with the one that I had used for ticket #2122.
Too late to commit this in 5.0.0 which is planned for this coming Monday. This will have to wait until 5.0.1 after the official 5.0.0 release.
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Checking...