On Thu, Jan 24, 2013 at 2:17 AM, Raif S. Naffah <r...@forge.com.au> wrote:
> this used to work in 2.2.2 --i just restarted a copy and verified, but > not anymore. Then this means the regression is caused by something environmental, not GeoServer itself, the fact it showed after an upgrade is likely incidental. However, one of the fixes we made in 2.2.4 was exactly to wipe out Filter.INCLUDE from the filter encoding chains, so I'm curious as to how it got there. Is it something we can reproduce, by getting access to the WFS server, the SLD, and the WMS request that triggers this? Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
