[Chameleon-dev] [Bug 610] New: [Chameleon] UploadContext widget doesn't maintain web.metadata information

bugzilla-daemon at www.maptools.org bugzilla-daemon at www.maptools.org
Tue Aug 3 17:58:58 EDT 2004


           Summary: [Chameleon] UploadContext widget doesn't maintain
                    web.metadata information
           Product: Chameleon
           Version: 1.99
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Widget
        AssignedTo: chameleon-dev at lists.maptools.org
        ReportedBy: dmorissette at dmsolutions.ca

Problem: when we load a context document with Chameleon and then save it back,
most of the top-level metadata elements (title, abstract, contact info, etc.)
are lost.

Background info: When a Map Context document is read by MapServer, a good number
of metadata fields from the context are stored in the map->web->metadata.
However, the UploadContext widget uses a temporary mapObj to read the context
file, and then manually copies selected fields from the temporary mapObj to the
main mapObj in the user's session.

I guess the first question is why do we do that? Why not just replace the mapObj
inside the session completely? The problem with this approach is that as
MapServer evolves, there may be more or less fields to copy, so this will always
be a potential source of problems.

Anyway, assuming there are good reasons to copy the mapObj members one by one,
then the code will have to be modified to maintain all the map->web->metadata
values that relate to the context so that they are properly written back if you
save the context document later on.

Here is a partial list of metadata fields that were lost and need to be transported:
  wms_contact*, wms_address*, etc.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the Chameleon-dev mailing list