[ http://issues.apache.org/jira/browse/DERBY-1383?page=comments#action_12415000 ]
Sunitha Kambhampati commented on DERBY-1383: -------------------------------------------- Thanks Kathey for filing this issue. Currently running the encodingTests suite will start server with default encoding and the client will run with UTF-16. Another area that might be good to test is, use the remote server testing to start the server with UTF-16 encoding and run the network server tests. > Run derbyall with derbyTesting.encoding=UTF-16 property to expose encoding > issues > ---------------------------------------------------------------------------------- > > Key: DERBY-1383 > URL: http://issues.apache.org/jira/browse/DERBY-1383 > Project: Derby > Type: Test > Components: Test > Versions: 10.1.2.1 > Reporter: Kathey Marsden > Priority: Minor > > In the past Derby, especially network server and client have had various bugs > related to code that is not portable due to encoding issues. It would be > good to get derbyall running with derbyTesting.encoding=UTF-16 to expose > any other issues and also to run it regularly to prevent regressions in this > area. > Note: > Sun JDK 1.5 has to be used to run with this property. It won't work with > jdk 1.4 or IBM JVMS. -- 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
