WFS using King.Oracle FDO Provider

[beginbenoit]

Currently, it is not possible to use the King.Oracle FDO Provider for WFS publication. Due to the way King.Oracle creates his class names (Schema~Table~GeometryField), it adds in characters that become invalid XML element names.

Here is an example of the error generated when trying to execute the GetFeature WFS command:

An exception occurred in FDO component. Element 'SIGIM_VSG~MAT_MUN_CR_S~LOC_GEOMETRY' is not a valid XML 1.0 element name.

The problem is somewhat tricky, as correcting it in the FDO Provider itself would mean changing how the class names are generated to remove the use of invalid characters, but that fix would invalidate all the existing Mapguide layers defined using the provider. Maybe the WFS interface could generate the XML using clean names that are mapped to the class names, but this would obviously have a performance hit. Hopefully a solution can be found.

[zspitzer]

yep, this annoying, that's why I proposed this

FDO RFC 43 - Standard FDO Class Naming Conventions ​http://trac.osgeo.org/fdo/wiki/FDORfc43

still, . isn't a valid part of a user, table or column name in oracle

so it would be safe to substitute . for ~ as a workaround

but we really ought to visit RFC 43 for 2.3

[jng]

Ticket retargeted after milestone closed

[jng]

Milestone renamed

[jng]

We can't do anything about this at the MapGuide level.

I think our official stance on this matter is to use the ​KingFdoClass feature to provide "clean" feature class names.