Re: [mapguide-users] WFS and the King Oracle FDO provider

[Philip Nell]

Thanks for looking into this Jackie.
So the guys at http://www.sl-king.com might have to look at it at the Oracle 
provider level at some point in the future.

We continue to use the KingFdoClass table described here:  
http://www.sl-king.com/fdooracle/KingFdoClass.htm 

Cheers

Philip Nell
Geospatial Solutions Architect 

Open Spatial | Tel: +61 2 9904 7077 | Mobile: +61 404 093 925

-Original Message-
From: mapguide-users [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf 
Of Jackie Ng
Sent: Wednesday, 4 May, 2016 10:49 PM
To: mapguide-users@lists.osgeo.org
Subject: Re: [mapguide-users] WFS and the King Oracle FDO provider

Just an update on this.

I'm not going to make the planned fix of scrubbing out '~' characters in the 
WFS response as this will most likely break how WFS clients are meant to
work:

 1. Request a WFS capabilities document
 2. Pick a WFS [encoded layer name]
 3. GetFeatures with the WFS [encoded layer name]  4. Process the GetFeatures 
response using the [encoded layer name] to determine how to extract the feature 
data whose elements will be named [encoded layer name]

The fix I had would've addressed step 4, but would break steps 1-3 as WFS 
would've still advertised the layer name with '~' and you would've still needed 
the layer name with '~' to make the GetFeatures request, and if we scrubbed the 
element name as per my planned fix it would break client behaviour on how to 
handle step 4.

Scrubbing the '~' in the GetCapabilities response in step 1 is not an option 
either, because at some point, we have to reverse translate that scrubbed layer 
name back to the FDO class name, so that the FDO queries will still work and 
there is no MapGuide-level configuration point currently that allows us to 
define such class name mappings so we can forward and reverse translate between 
FDO class names and WFS encoded layer names. This is primarily something FDO 
providers provide (excuse the pun) through the configuration document 
mechanism, or in the case of the King.Oracle provider, the KingFdoClass special 
table.

So long story short, '~' was a *very poor* choice of delimiting character used 
by the King.Oracle FDO provider that we currently can't workaround at the 
MapGuide-level. Use the KingFdoClass mechanism to provide "clean" class names 
that won't break WFS responses.

- Jackie



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/WFS-and-the-King-Oracle-FDO-provider-tp5256626p5264530.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] WFS and the King Oracle FDO provider

[Jackie Ng]

Just an update on this.

I'm not going to make the planned fix of scrubbing out '~' characters in the
WFS response as this will most likely break how WFS clients are meant to
work:

 1. Request a WFS capabilities document
 2. Pick a WFS [encoded layer name]
 3. GetFeatures with the WFS [encoded layer name]
 4. Process the GetFeatures response using the [encoded layer name] to
determine how to extract the feature data whose elements will be named
[encoded layer name]

The fix I had would've addressed step 4, but would break steps 1-3 as WFS
would've still advertised the layer name with '~' and you would've still
needed the layer name with '~' to make the GetFeatures request, and if we
scrubbed the element name as per my planned fix it would break client
behaviour on how to handle step 4.

Scrubbing the '~' in the GetCapabilities response in step 1 is not an option
either, because at some point, we have to reverse translate that scrubbed
layer name back to the FDO class name, so that the FDO queries will still
work and there is no MapGuide-level configuration point currently that
allows us to define such class name mappings so we can forward and reverse
translate between FDO class names and WFS encoded layer names. This is
primarily something FDO providers provide (excuse the pun) through the
configuration document mechanism, or in the case of the King.Oracle
provider, the KingFdoClass special table.

So long story short, '~' was a *very poor* choice of delimiting character
used by the King.Oracle FDO provider that we currently can't workaround at
the MapGuide-level. Use the KingFdoClass mechanism to provide "clean" class
names that won't break WFS responses.

- Jackie



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/WFS-and-the-King-Oracle-FDO-provider-tp5256626p5264530.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] WFS and the King Oracle FDO provider

[Philip Nell]

Hi Jacki,

If you want to send me the fix and rough test procedure we can do a quick test
We have quite a few Oracle instances and MGOS 2.6.1.8732 installations.

Regards

Philip Nell
Geospatial Solutions Architect

Open Spatial | Tel: +61 2 9904 7077 | Mobile: +61 404 093 925

From: Jackie Ng [via OSGeo.org] [mailto:ml-node+s1560n5258775...@n6.nabble.com]
Sent: Wednesday, 30 March 2016 7:22 PM
To: Philip Nell 
Subject: Re: WFS and the King Oracle FDO provider

I have a fix in place for this, which basically scrubs out any characters like 
'~' that are illegal in an XML element context from FDO class names before it 
is outputted as a GML feature element name.

Just need to find out the most painless way to spin up an oracle xe instance to 
verify the fix.

- Jackie

If you reply to this email, your message will be added to the discussion below:
http://osgeo-org.1560.x6.nabble.com/WFS-and-the-King-Oracle-FDO-provider-tp5256626p5258775.html
To unsubscribe from WFS and the King Oracle FDO provider, click 
here.
NAML




--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/WFS-and-the-King-Oracle-FDO-provider-tp5256626p5258901.html
Sent from the MapGuide Users mailing list archive at Nabble.com.___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] WFS and the King Oracle FDO provider

[Jackie Ng]

I have a fix in place for this, which basically scrubs out any characters
like '~' that are illegal in an XML element context from FDO class names
before it is outputted as a GML feature element name.

Just need to find out the most painless way to spin up an oracle xe instance
to verify the fix.

- Jackie



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/WFS-and-the-King-Oracle-FDO-provider-tp5256626p5258775.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] WFS and the King Oracle FDO provider

[Philip Nell]

Hi Rémy,

Thank you VERY much for your advice on using table KINGFDOCLASS to rename the 
FDO classes
Also thanks to Google for translating  the French to English and getting me to 
this procedure (http://www.sl-king.com/fdooracle/KingFdoClass.htm) which I 
followed and it solved my problem!

The underlying issue with the ~ remains though.

Regards

Philip Nell
Geospatial Solutions Architect

Open Spatial | Tel: +61 2 9904 7077 | Mobile: +61 404 093 925

From: mapguide-users [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf 
Of Rémy Gourrat
Sent: Wednesday, 16 March 2016 7:32 PM
To: MapGuide Users Mail List <mapguide-users@lists.osgeo.org>
Subject: Re: [mapguide-users] WFS and the King Oracle FDO provider

Hi,

Your url link is broken.

Is this an issue with ~ separator in class name ?

Si oui, vous pouvez contourner spécifier votre propre nom de classe en 
utilisant la table KINGFDOCLASS

Rémy
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] WFS and the King Oracle FDO provider

[Jackie Ng]

If '~' is an illegal character for XML element names, would MapGuide
replacing it with some other legal character (maybe '-' or '_') be a
sufficient solution?

Haven't read the WFS spec, so I don't know if the above solution violates
any rules in the specification.

- Jackie



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/WFS-and-the-King-Oracle-FDO-provider-tp5256626p5256750.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] WFS and the King Oracle FDO provider

[Rémy Gourrat]

Hi,

Your url link is broken.

Is this an issue with ~ separator in class name ?

Si oui, vous pouvez contourner spécifier votre propre nom de classe en 
utilisant la table KINGFDOCLASS

Rémy
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users