[ http://jira.jboss.com/jira/browse/JBPM-958?page=all ] David Chan updated JBPM-958: ---------------------------- Attachment: rushcode.JPG the page was displayed. The strange character may come out because wrong encoding specified, but I don't know where I can change the encoding setting. I have debugged the whole console application one day. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-958?page=comments#action_12363887 ] David Lloyd commented on JBPM-958: ---------------------------------- I think you're seeing a known issue with how Tomcat interacts with different encodings. The problem is that the HTTP and HTML specs really don't mention anything about what character set or encoding should be used for URL-encoded values (including GET parameters and postback values). So different containers default to different settings. In order to fix this issue, open the deploy/jboss-web.deployer/server.xml in your server directory (it will be server/default or server/jbpm unless you've customized something). Edit the <Connector> entry that references port 8080 and add the following attribute: useBodyEncodingForURI="true" So the whole XML element should look something like this: <Connector port="8080" address="${jboss.bind.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" useBodyEncodingForURI="true" /> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-958?page=comments#action_12364483 ] David Chan commented on JBPM-958: --------------------------------- I have fixed this problem, it doesn't care with JBoss-tomcat connector. I even rewrote some parts of this console application and want to issue a Chinese language pack of the whole jBPM which include message, jsf components, UI, and some additions like FileUpload, data type bound etc.. Can I be a jBPM contributor? I have time, experience and patience, the most important is that I really like BPM and want to be a guru. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-958?page=comments#action_12365969 ] David Chan commented on JBPM-958: --------------------------------- Yes, I fixed this problem in my new reworked console application which supports eastern character perfectly now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-958?page=comments#action_12385510 ] Jorge commented on JBPM-958: ---------------------------- I am having the same problems with special characters (ç,â,ã, etc..). For example, I enter in the form "PEÇA", but it saves " PEÇAS". Also, I cannot name task-nodes with special characters..I get Invalid byte 2 of 3-byte UTF-8 sequence when jbpm tries to read de gdp.xml/processdefinition.xml I made the changes suggested by David Lloyd, editting <Connector> entry in the server.xml, but the problem persists. Can anyone help? I was wondering if David Chan would tell how he apparently fixed the problem. Environment Used: Windows XP Professional English JDK 1.6 Eclipse 3.2.2 JPDL Suite 3.2 GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-958?page=comments#action_12386259 ] Jorge commented on JBPM-958: ---------------------------- I have tried the official solution, but it does not solve the problem. Any other ideas? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira