What I have done; Tried all the settings as suggested so far in this thread... switching everything to UTF-8 - checked ALL my files for any sign of ISO... (to avoid mixing concerns) ... still no luck! Looked in the offending forms and found the   reference - when I removed that then everything worked. This is OK, BUT I do not understand what the real issue/cause is here, or why forms do not display a simple UNICODE character? Any clarification would help me (and maybe others) avoid this nasty issue!
>>> [EMAIL PROTECTED] 2006/02/07 03:58:54 PM >>> first thought: i think we had this error message when using escaped utf-8 chars... our source files are encoded in utf-8, and some guy inserted a escaped " " in utf 8 with is in utf-8 (<!ENTITY *nbsp* " ">) this crashed the forms. didn't figure out why, not enough time, just threw out the escaped chars. but as you are using iso-8859-1, just search for a file that's not in the right encoding, or a string 160 in your form files and delete this... (ultraedit or grep, depending on your system :-) ) probably one of your coders or editors uses utf-8, so you'll accidently inserted this utf-8 fragment (and doesn't know it :-) ) second thought: are you sure that the configuration is the same ? maybe the app server has other defaults, that you don't set in your application config... no server admin guru, but we had problems in this area. Maybe it helps to set some init-params in web.xml, here comes a snippet from my app (replaced my setting utf-8 with your setting iso-8859-1) <!-- Set encoding used by the container. If not set the ISO-8859-1 encoding will be assumed. --> <init-param> <param-name>container-encoding</param-name> <param-value>ISO-8859-1</param-value> </init-param> <!-- Set form encoding. This will be the character set used to decode request parameters. If not set the ISO-8859-1 encoding will be assumed. --> <init-param> <param-name>form-encoding</param-name> <param-value>ISO-8859-1</param-value> </init-param> hth, tom Derek Hohls wrote: > I am struggling to get forms displayed on a server - > UNIX machine running Cocoon 2.1.5 and JDK 1.4 > (the same app works **fine** on the development > machine, running the same configuration, as well as > on a Linux server...) > > The error message I get when trying to show the form > (filled with data from the database) is: > > org.apache.cocoon.ProcessingException: > Failed to execute pipeline.: > java.lang.RuntimeException: > org.xml.sax.SAXException: > Attempt to output character of integral value 160 that is not represented in > specified output encoding of . > > [and no, there is no word missing just before the above "full stop"] > > Based on mailing list and wiki suggestions I have tried: > > <form action=... method="post" accept-charset="ISO-8859-1"> > > also: > > <?xml version="1.0" encoding="ISO-8859-1"?> > > in the form, *and* the stylesheet processing the form for display > > also, in cocoon.xconf > > <jdbc name="pool_name"> > <pool-controller min="5" max="10"/> > <dburl>jdbc:mysql://YourHostName:3360/YourDataBaseName?useUnicode=true&characterEncoding=ISO-8859-1</dburl> > <user>database_user</user> > <password>database_password</password> > </jdbc> > > > NB - I am not trying to use any complex characters - inputs > should be "plain" English! > > Is there a "Definitive Guide to Using Encoding" anywhere?? > > Thanks > Derek > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to [EMAIL PROTECTED] This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
