Update:
I found the layer and the UI does not let me go to the 'Publishing' tab:
- Field 'latLonBoundingBox' is required.
- Field 'Declared SRS' is required.
It was one of the layers that was uploaded programatically via the REST API,
my guess is that it should be disabled by default instead of enabled and
breaking the GetCaps.
Is this as a bug in the behavior of the REST API (not verifying if the
layers that are configured that way can be served)?
Ariel.
On Thu, Sep 8, 2011 at 5:32 PM, Ariel Nunez <[email protected]>wrote:
> Hello people,
>
> I am experiencing a problem with my GeoServer the GetCapabilities of the
> WMS is broken [1]. My questions are:
>
> #1 How can I diagnose which layer is causing this? I end up with a
> NullPointerException [2].
>
> #2 Why does GeoServer return an invalid XML (and XML file inside another
> XML file)? I remember some settings about optimizing for speed vs optimizing
> for 'correctness' in earlier versions of GeoServer but I don't see that now
> [3].
>
> #3 What changes would be needed in GeoServer to better diagnose (or if
> possible self correct) this problem. This is an application where GeoServer
> is used as a backend storage and I would like to avoid a failed layer upload
> via the REST API from totally breaking the server :(
>
>
> Thanks in advance for any help you can provide, I addressed this to the dev
> list because I intend to follow up with a patch to come with a more helpful
> behavior to the GeoServer Admin / User.
>
> Ariel
>
>
> [1] Trimmed version of the output:
>
> ------------ start of the document ------------
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE WMT_MS_Capabilities SYSTEM "
> http://demo.riskinabox.org:80/geoserver-geonode-dev/schemas/wms/1.1.1/WMS_MS_Capabilities.dtd
> ">
> <WMT_MS_Capabilities version="1.1.1" updateSequence="1704">
> <Service>
> <Name>OGC:WMS</Name>
> <Title>My GeoServer WMS</Title>
>
> [snip ... ]
> <SRS>EPSG:62786405</SRS>
> <SRS>EPSG:62796405</SRS>
> <SRS>EPSG:62806405</SRS>
> <SRS><?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
> ServiceExceptionReport SYSTEM "
> http://demo.riskinabox.org:80/geoserver-geonode-dev/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd";>
> <ServiceExceptionReport version="1.1.1" > <ServiceException>
> javax.xml.transform.TransformerException: Translator error
> Translator error
> null
> </ServiceException></ServiceExceptionReport>
> -----------------End of the document -------------
>
> [2] http://dpaste.de/1ICYK/
>
> [3] Information about GeoServer
> Build Information
>
> - Version2.1-SNAPSHOT
> - Subversion Revision16252
> - Build Date17-Aug-2011 00:28
> - GeoTools Version2.7-SNAPSHOT (rev 37850)
>
>
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
