Hi Justin Thanks for response. I'll try with nightly build to check.
About breaking the WMS if one layer is in error, in my opinion should not be a problem if the error provided helps to identify which layer or layer group is in error, but now the Translator error is not very useful, also the stacktrace doesn't give any information about where is the error, so it's difficult to find. Regards, Jose García On Tue, Mar 1, 2011 at 4:31 PM, Justin Deoliveira <[email protected]>wrote: > Hi Jose, > > I am not 100% sure but I seem to remember some fixes to layer group handing > with respect to this that occurred after 2.0.2. I could be wrong though. > Regardless as 2.0.2 is quite old at this point it would be nice to know if > indeed it has been fixed. Any chance you can try a nightly to see if the > issue persists? > > As for not breaking the WMS if one layer is in error... it was decided a > while back that it would be better to fail fast and break the WMS rather > than let the layer go misconfigured silently. However I do agree that there > are cases in which this behaviour is not ideal. It would be nice to be able > to control this with a config option. Feel free to open a feature request > for this. > > -Justin > > On Mon, Feb 28, 2011 at 8:25 AM, jose garcia <[email protected]> wrote: > >> Hi >> >> I create a layer group in GeoServer 2.0.2, when add the first layer and >> generate the bounding box seem ok: EPSG:4326 is shown for SRS and the >> correct box is calculated. Requesting WMS Capabilities document is ok. >> >> Later adding another layer to group and regenerating the bounding box no >> error, but editing the group again i get UNKOWN SRS and next to Find button: >> "WGS84(DD)" that is strange as no layer has this SRS. Requesting WMS >> Capabilities document fails with this error: >> >> <?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <!DOCTYPE ServiceExceptionReport SYSTEM " >> http://85.214.33.34:80/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd";> >> >> <ServiceExceptionReport version="1.1.1" > >> <ServiceException> >> Translator error >> Translator error >> 0 >> </ServiceException> >> </ServiceExceptionReport> >> >> >> No matter the order use to add layers in the group, with the first layer >> is ok but after adding a second layer and regenerate the bounding box the >> problem is there. Removing the layer group, WMS Capabilities document is ok >> again. >> >> Any idea what can cause this? Also is possible to catch these things to >> not break WMS service? >> >> Thanks and regards, >> Jose García >> >> >> ------------------------------------------------------------------------------ >> Free Software Download: Index, Search & Analyze Logs and other IT data in >> Real-Time with Splunk. Collect, index and harness all the fast moving IT >> data >> generated by your applications, servers and devices whether physical, >> virtual >> or in the cloud. Deliver compliance at lower cost and gain new business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> _______________________________________________ >> Geoserver-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> >> > > > -- > Justin Deoliveira > OpenGeo - http://opengeo.org > Enterprise support for open source geospatial. > >
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
