Opened 15 years ago
Closed 14 years ago
#2908 closed defect (fixed)
setConnectionType(MS_WMS) doesn't work with mapscript
Reported by: | assefa | Owned by: | mapserverbugs |
---|---|---|---|
Priority: | normal | Milestone: | 5.4 release |
Component: | MapServer C Library | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: | sdlime, adube@… |
Description
reported by Alexander Dube:
I just installed mapserver 5.4.0-beta1. In mapscript, I'm now not unable to use oLayer->set("connectiontype", MS_WMS). I get an error saying "use setConnectionType()" instead.
That's what I did, but it doesn't work with MS_WMS. My collegue Julien looked deeper in the code and found out in maplayer.c, in the msInitializeVirtualTable, when we use MS_WMS it returns MS_FAILURE.
So I guess it's no longer possible to set connectiontype to wms in mapscript. Is there a new way of doing this ?
Also, why would a normal mapfile still accept the wms CONNECTIONTYPE ? I tried to save my map object as a mapfile and only added CONNECTIONTYPE wms and it worked.
Attachments (1)
Change History (8)
by , 15 years ago
Attachment: | diff_2908.txt added |
---|
comment:1 by , 15 years ago
Cc: | added |
---|---|
Milestone: | → 5.4 release |
Steve,
This seems to work for me but would like to verify with you before commiting.
Note that I have set the target to 5.4 but I can also go to 5.4.1 if appropriate.
Alexandre, can you please try the patch and report?
Thanks
comment:3 by , 15 years ago
Assefa, the patch seems fine so I think we should commit it before 5.4.0beta4. Do you want to do it or should I do it?
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
I reopen this, because I still found a problem with this. Currently when setting the connectiontype to MS_WMS the type is changed internally to MS_RASTER and the layer is not drawn.
comment:6 by , 15 years ago
Component: | MapScript-PHP → MapServer C Library |
---|
comment:7 by , 14 years ago
Milestone: | 5.6 release → 5.4 release |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
Tamas, I believe we can mark this one closed in 5.4? Please reopen with a comment if not.
patch to fix the problem