[fdo-users] RE: [mapguide-internals] FeatureSource encoding of
layers
Tom Fukushima
tom.fukushima at autodesk.com
Tue Aug 19 16:25:20 EDT 2008
Hi Kenneth,
That particular document is created by FDO, could you post this question to the FDO users mailing list? Oh, wait, I just did.
Tom
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
Sent: Monday, August 18, 2008 2:26 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] FeatureSource encoding of layers
I have some bug reports regarding wrong encoding of spaces and other
characters:
http://trac.osgeo.org/mapguide/ticket/635
http://trac.osgeo.org/mapguide/ticket/662
After checking up on the problem, it turns out that the
"DESCRIBEFEATURESCHEMA" returns an xml with these encoded characters.
The characters turn up in the class name part of the xml (name, type,
key, selector elements).
It is easy to detect and re-code, as they are of the form -x00- where 00
is the charaters hex value.
Entering either the encoded or unencoded value into the Schema field of
the "DESCRIBEFEATURESCHEMA" call, gives the same results.
The question is, why are they there?
When, if ever, should the names be passed encoded to the server?
Are there a better call that does not encode the names?
(GETCLASSES returns the unencoded names, but no column data)
--
Regards, Kenneth Skovhede, GEOGRAF A/S
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
More information about the fdo-users
mailing list