[mapserver-dev] Using updateFromString on existing items

Lime, Steve D (MNIT) steve.lime at state.mn.us
Mon Oct 9 07:23:30 PDT 2017

The original use case was to facilitate minor edits to existing object properties but not sub-objects. For example, you can't replace all the classes in a layer through a string update to the layer itself. We certainly could make all that work cleaner if there were demand.

At least you get a proper error message... ;-)


From: mapserver-dev <mapserver-dev-bounces at lists.osgeo.org> on behalf of Tamas Szekeres <szekerest at gmail.com>
Sent: Sunday, October 8, 2017 12:49:55 PM
To: mapserver-dev at lists.osgeo.org
Subject: [mapserver-dev] Using updateFromString on existing items

Hi Devs,

Is that a supported use case to apply updateFromString on an existing item or it should only be used only on a newly created item?

For example when I use layerObj.updateFromString on an existing layer I get the following error

loadProjection(): General error message. Projection is already initialized. Multiple projection definitions are not allowed in this object. (line 10)

This is because we don't have a proper cleanup code on the existing layer before calling loadLayer on it. The same applies to the other object types.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20171009/80493ca7/attachment.html>

More information about the mapserver-dev mailing list