Hi, I lost the original mail I posted, so I'm starting a new thread.
I'm now convinced that there is a bug in Geotools when they create the XML for querying a WFS. Given a Java string that contains non-ascii characters and is used as literal expression in a LikeFilter, geotools takes this java string (or eventually the whole generated xml) and creates a bytestream that is encoded in the system encoding. Bad idea, the WFS receives a HTTP POST request that is itself utf-8 encoded. The content beeing an xml document that is declared to be utf-8 encoded as well, but in fact it's encoded in the systems encoding. So far I have been able to reproduce this on two different linux boxes, just setting the system encoding to latin9 (i.e. [EMAIL PROTECTED] for LC_CTYPE, LANG=C). I'm using geotools 2.0 atm and am just asking here to get a comment on this, before I file a bugreport on the gt2 website. Andreas ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
