[ http://issues.apache.org/jira/browse/DERBY-900?page=comments#action_12376551 ]
Kathey Marsden commented on DERBY-900: -------------------------------------- I am trying to understand the type of case that would cover the code changed and trigger the encoding problem. Do you have any idea what that case might be? Kathey > Remove use of String(byte[]) and String(byte[], int, int) constructors in > network client leading to non-portable behaviour > -------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-900 > URL: http://issues.apache.org/jira/browse/DERBY-900 > Project: Derby > Type: Bug > Components: Network Client > Reporter: Daniel John Debrunner > Assignee: Sunitha Kambhampati > Fix For: 10.2.0.0 > Attachments: Derby900.p2.diff.txt, TestEnc.java, derby900.diff.p1.txt, > derby900.p2.stat.txt, derby900.stat.p1.txt, derby900.test.diff.txt, > derby900.test.stat.txt, for_10.1_derby900.diff.p1.txt, > for_10.1_derby900.stat.p1.txt > > These constructors use the Java default platform encoding to convert the > bytes to a String, this typically leads to bugs on platforms with different > encodings. > Replace with code using fixed conversion, or alternative mechanisms. > If the call is required its use should be commented as to why it is required. > org.apache.derby.client.am.ClobOutputStream - some existing bug? > org.apache.derby.client.am.DateTime - see DERBY-877 > org.apache.derby.client.am.sqlca > I generated this list using the Java search in eclipse for references to the > constructors > String(byte[]) > String(byte[],int,int) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
