[mapguide-users] MG 2.1 Beta and WMS / FDO Exception

[braccos]

Crispin,

 

I'm running with MGOS 2.1 and WMS Server MapServer 5.4.2 connected to
Oracle 11g.

And everything is working correctly.

 

Stefano

 

 

From: Crispin_at_1Spatial [via OSGeo.org]
[mailto:ml-node+4149962-21050104 at n2.nabble.com] 
Sent: Friday, 11 December, 2009 09:21
To: Bracco Stefano
Subject: Re: [mapguide-users] MG 2.1 Beta and WMS / FDO Exception

 

Update. 

WMS is tricky but with an appropriate "config" file and coordinate
system overrides in place we have MapGuide 2.1 test instances reading
from ArcGIS (9.2 I think), Smallworld and MapServer WMS servers. 

I *guess* that the "Invalid format for the EXCEPTION parameter" issue
that MG(FDO) throws is with the way that MG(FDO) forms the WMS URL - the
client (MG) should check the service capabilities for what types of
exception are supported - eg XML, TXT and request appropriately.
Otherwise some request will fail but the exception type requested is not
supported by the server.  For example, the service that gave me issues
had this in the capabilities (though so did the valid ones!): 

                <Exception> 
                        <Format>application/vnd.ogc.se_xml</Format> 
                        <Format>application/vnd.ogc.se_inimage</Format> 
                        <Format>application/vnd.ogc.se_blank</Format> 
                </Exception> 


I'm no reader of OGC/WMS documentation though and don't have fiddler
set-up to see the request that was being passed.  That would be a help. 

Finally, setting a coordinate override on the WMS but then removing the
coordinate system from the .MapDefinition helped in at least one case
bizzarely. 

We get WMS integration requests for about 25% of our installations now
so having a reliable automated config builder (Maestro?), coordinate
understanding and stable provider will become increasingly valuable as
knowledge and especially for newcomers. 

Crispin_at_1Spatial wrote:

I have a WMS connection that runs OK on a MapGuide 2.0.2 server --
verified today.  I have taken the same settings over to MG 2.1 and get
an FDO error. 

MapGuide Server (Version 2.1.0.3891) 
MapGuide Site Administrator (Version 2.1.0.3891) 

An exception occurred in FDO component. InvalidFormat:
msWMSLoadGetMapParams(): WMS server error. Invalid format for the
EXCEPTION parameter. 

This occurs when I preview my .FeatureSource (using Maestro) and then
click the "View Data" to invoke the second panel in the DescribeSchema
interface... of course I get no layers to display with the same message
written to the log files. 

Before I log a ticket for the regression I have a quick query on the
format of the config file... as per the instructions at...
https://trac.osgeo.org/fdo/wiki/FdoWmsNotes

I have the following line that references "OSGeo.WMS.3.1" -- is this
correct for FDO 3.4 / MG 2.1? 
It is certainly OK for FDO 3.3 / MG 2.0.2. 

  <SchemaMapping provider="OSGeo.WMS.3.1" name="WMS"
xmlns="http://fdowms.osgeo.org/schemas"> 

Anyone got WMS running with MG 2.1? 

 Thanks in advance - Crispin 

 

________________________________

View message @
http://n2.nabble.com/MG-2-1-Beta-and-WMS-FDO-Exception-tp3650617p4149962
.html 
To unsubscribe from MG 2.1 Beta and WMS / FDO Exception, click here
< (link removed) 
jY29AZXVyYWMuZWR1fDM2NTA2MTd8LTQ0ODc1MzY5Ng==> . 

 


-- 
View this message in context: http://n2.nabble.com/MG-2-1-Beta-and-WMS-FDO-Exception-tp3650617p4150040.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20091211/f52ccaba/attachment.html