[
https://issues.apache.org/jira/browse/DERBY-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner closed DERBY-900.
---------------------------------------
Assignee: (was: Sunitha Kambhampati)
Confirmed no use of these non-portable constructors in the network client code.
Should remain assigned to Sunitha, but she is not present in the drop down list
and it seems no way to leave the assign to field as-is.
> Remove use of String(byte[]) and String(byte[], int, int) constructors in
> network client leading to non-portable behaviour
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-900
> URL: https://issues.apache.org/jira/browse/DERBY-900
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6
> Reporter: Daniel John Debrunner
> Fix For: 10.1.3.1, 10.2.1.6
>
> Attachments: derby900.diff.p1.txt, Derby900.p2.diff.txt,
> derby900.p2.stat.txt, derby900.p2_encodingChange.diff.txt,
> derby900.stat.p1.txt, derby900.test.diff.txt, derby900.test.stat.txt,
> derby900_p2_cleanup.diff.txt, derby900_p2_cleanup.stat.txt,
> for_10.1_derby900.diff.p1.txt, for_10.1_derby900.stat.p1.txt, TestEnc.java,
> testsecmec.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
