John, We had a problem with certain data not being xml-rpc compliant, and got around it by gzipping the data. The gzipped data is XML-RPC compliant, and in our case, the compression helped transfer rates since the data was large enough to justify the compression/decompression time. Just an idea, Derek
-----Original Message----- From: John Luxford [mailto:[EMAIL PROTECTED] Sent: Thursday, November 11, 2004 12:03 PM To: [EMAIL PROTECTED] Subject: Anyone know a filter I can use to prevent this? Hi, I'm getting the following error when I try to compose a response message with values from a Lucene index: Server Error (0) org.apache.xmlrpc.XmlRpcException: Invalid character data corresponding to XML entity ? I've narrowed it down to a specific field and a specific record causing the problem (there are many others, but I've isolated one for testing), but I'm not sure of the best way to filter these characters without simply removing them -- ie. to make them valid for sending through Apache XML-RPC. The isolated error appears to be caused by an apostrophe character originally from MS Word, but several others are causing the same problem, and the solution would need to solve the problem itself instead of replacing specific characters. Is there an encoding function, or an encoding setting I can use to prevent this? Any info you have would be greatly appreciated. Thanks in advance, Lux -- John Luxford President and Chief Developer ______________________________ Simian Systems Inc. Evolve Your Business ______________________________ web : http://www.simian.ca/ email : [EMAIL PROTECTED] phone : 204.942.8630 fax : 309.218.3874
