<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'>Crispin,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'>I’m running with MGOS 2.1 and WMS Server MapServer 5.4.2
connected to Oracle 11g.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'>And everything is working correctly.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'>Stefano<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Crispin_at_1Spatial
[via OSGeo.org] [mailto:<a href="http://n2.nabble.com/user/SendEmail.jtp?type=node&node=4150040&i=0" target="_top" rel="nofollow">[hidden email]</a>] <br>
<b>Sent:</b> Friday, 11 December, 2009 09:21<br>
<b>To:</b> Bracco Stefano<br>
<b>Subject:</b> Re: [mapguide-users] MG 2.1 Beta and WMS / FDO Exception<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Update. <br>
<br>
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. <br>
<br>
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!): <br>
<br>
<Exception> <br>
<Format>application/vnd.ogc.se_xml</Format> <br>
<Format>application/vnd.ogc.se_inimage</Format> <br>
<Format>application/vnd.ogc.se_blank</Format> <br>
</Exception> <br>
<br>
<br>
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. <br>
<br>
Finally, setting a coordinate override on the WMS but then removing the
coordinate system from the .MapDefinition helped in at least one case
bizzarely. <br>
<br>
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. <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><b>Crispin_at_1Spatial wrote:<o:p></o:p></b></p>
</div>
<div>
<p class=MsoNormal>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. <br>
<br>
MapGuide Server (Version 2.1.0.3891) <br>
MapGuide Site Administrator (Version 2.1.0.3891) <br>
<br>
An exception occurred in FDO component. InvalidFormat: msWMSLoadGetMapParams():
WMS server error. Invalid format for the EXCEPTION parameter. <br>
<br>
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. <br>
<br>
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... <a href="https://trac.osgeo.org/fdo/wiki/FdoWmsNotes" target="_top" rel="nofollow">https://trac.osgeo.org/fdo/wiki/FdoWmsNotes</a><br>
<br>
I have the following line that references "OSGeo.WMS.3.1" -- is this
correct for FDO 3.4 / MG 2.1? <br>
It is certainly OK for FDO 3.3 / MG 2.0.2. <br>
<br>
<SchemaMapping provider="OSGeo.WMS.3.1"
name="WMS" xmlns="<a href="http://fdowms.osgeo.org/schemas" target="_top" rel="nofollow">http://fdowms.osgeo.org/schemas</a>"> <br>
<br>
Anyone got WMS running with MG 2.1? <br>
<br>
Thanks in advance - Crispin <o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=1 width="100%" noshade style='color:#CCCCCC' align=center>
</div>
<div>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"Tahoma","sans-serif";
color:#666666'>View message @ <a href="http://n2.nabble.com/MG-2-1-Beta-and-WMS-FDO-Exception-tp3650617p4149962.html" target="_top" rel="nofollow">http://n2.nabble.com/MG-2-1-Beta-and-WMS-FDO-Exception-tp3650617p4149962.html</a>
<br>
To unsubscribe from MG 2.1 Beta and WMS / FDO Exception, <a target="_top" rel="nofollow">click
here</a>. <o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<br><hr align="left" width="300">
View this message in context: <a href="http://n2.nabble.com/MG-2-1-Beta-and-WMS-FDO-Exception-tp3650617p4150040.html">RE: [mapguide-users] MG 2.1 Beta and WMS / FDO Exception</a><br>
Sent from the <a href="http://n2.nabble.com/MapGuide-Users-f1803227.html">MapGuide Users mailing list archive</a> at Nabble.com.<br>