incomplete or no WMS Capabilities and database stores

[bartvde@…]

When using the Oracle Spatial datastore, no WMS capabilities are generated (the
request times out) because the msOracleSpatialLayerGetExtent() function is not
implemented. You have to set a WMS_EXTENT metadata in order to get capabilities.

But this seems to be a general problem of the WMS capabilities, if some error
occurs, incomplete WMS capabilities or no capabilities at all are returned.

Should something be changed in the WMS capabilities behaviour, so that a
serviceexception is generated, or a warning?

Or is this specific to the oracle spatial datastore?

[dmorissette]

Unfortunately the way WMS Capabilities are currently generated, we cannot easily
change them to produce a clean exception if an error happens in the middle of
generating capabilities. This is really not something that happens often anyway:
normally if a server is able to serve capabilities once during testing then it
always works later on.

So I think the easier fix for this is to implement the missing function. I'll
reassign to Fernando for that. Also setting 4.6 target milestone.

BTW, to test this, Fernando, you can use a URL like the following on any mapfile
that contains an oracle layer that does NOT have a WMS_EXTENT metadata:
http://your.host/cgi-bin/mapserv?map=/path/to/mapfile.map&version=1.1.1&request=GetCapabilities

[fsimon@…]

Fixed in CVS version of maporaclespatial.c in Mapserver 4.5.
Thanks.
    

[bartvde@…]

If I leave out wms_extent now from the METADATA, Mapserver correctly calculates
the bbox:

        <LatLonBoundingBox minx="3.20548" miny="50.7342" maxx="7.24475"
maxy="53.584" />
        <BoundingBox SRS="EPSG:28992"
                    minx="10426.3" miny="306846" maxx="278026" maxy="621876" />