[Geoserver-devel] [jira] Created: (GEOS-4699) no capabilities request possible with wrong coverage configuration

no capabilities request possible with wrong coverage configuration
------------------------------------------------------------------

                 Key: GEOS-4699
                 URL: https://jira.codehaus.org/browse/GEOS-4699
             Project: GeoServer
          Issue Type: Bug
          Components: Configuration
    Affects Versions: 2.1.1
            Reporter: Tobias Warneke
            Assignee: Justin Deoliveira

Migrating from geoserver 1.7.x to 2.1.x we had some coverage stores where the raster file doesnt exist anymore. Having such coverages within GeoServer 2.1.x it is not possible to do a capabilities request. It stops with an xml - error message within a 'partial' capabilities document.

-------------
<Layer>
                <Name>9</Name>
                <Title>9</Title>
                <Layer queryable="1">
                  <Name>leuna:leuna_945</Name>
                  <Title>4638SO</Title>
                  <Abstract/>
                  <KeywordList>
                    <Keyword>4638SO</Keyword>
                  </KeywordList>
                  <CRS>EPSG:31468</CRS>
                  <CRS>CRS:84</CRS>
                  <EX_GeographicBoundingBox>
        <?xml version="1.0" encoding="UTF-8"?><ServiceExceptionReport version="1.3.0" xmlns="http://www.opengis.net/ogc&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation="http://www.opengis.net/ogc http://192.168.12.3:8883/geoserver/schemas/wms/1.3.0/exceptions_1_3_0.xsd&quot;&gt; <ServiceException>
      javax.xml.transform.TransformerException: Translator error
Translator error
Error occurred trying to write out metadata for layer: leuna_783
Unable to acquire a reader for this coverage with format: WorldImage
</ServiceException></ServiceExceptionReport>
------------------

It would be nice if geoserver could disable this layer but continues to work without any problem.

best regards

Tobias

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira