On Wed, Jan 12, 2011 at 10:56 PM, Chris Holmes <[email protected]> wrote: > Hmmm... So there's nothing we can do to code around it at the GeoServer or > GeoTools level. > > How about we just remove that layer from the default data? It seems to be > the only one affected. I feel like it'd be good to make a better impression > on the latest tomcats than bombing on any WMS Capabilities request, and then > having to adjust some obscure settings. Most users will just move on to > another product by that time.
What I'm wondering more is why the WMS 1.3 capabilities transformer tries to perform data access to start with (getting a reader) Do we do the same for the WMS 1.1 one? Cheers Andrea -- Ing. Andrea Aime Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584962313 fax: +39 0584962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ----------------------------------------------------- ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
