[
https://issues.apache.org/jira/browse/DERBY-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606373#action_12606373
]
Knut Anders Hatlen commented on DERBY-1726:
-------------------------------------------
For the record, I managed to get LocalizedDisplayScriptTest running in my
timezone by adding this to setUp():
defaultTimeZone = TimeZone.getDefault();
TimeZone.setDefault(TimeZone.getTimeZone("America/Los_Angeles"));
And adding this to tearDown():
TimeZone.setDefault(defaultTimeZone);
Since the class javadoc for java.util.TimeZone explicitly mentions that
"America/Los_Angeles" gives U.S. Pacific Time, I'd assume it's fairly portable.
Two other comments:
- It would be good to add a comment to
LocalizedResource.resetLocalizedResourceCache() explaining what it does, and
perhaps why it is needed.
- In LocalizedAttributeScriptTest, I think it's better to use ISO-8859-1 than
Cp850, since the former must be supported by all JVMs. The changes you made to
the canon also work with ISO-8859-1 encoding.
> Make i18n/LocalizedDisplay.sql and i18n/LocalizedConnectionAttribute.sql
> behave equally on different platforms
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1726
> URL: https://issues.apache.org/jira/browse/DERBY-1726
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: DERBY-1726_1.diff, DERBY-1726_2.diff, DERBY-1726_3.diff,
> DERBY-1726_3.stat, DERBY-1726_4.diff, props.java
>
>
> Myrna van Lunteren commented on DERBY-244:
> The one remark I have is that I still cannot get the LocalizedDisplay.sql and
> LocalizedConnectionAttribute.sql test from the i18n directory to behave the
> same under windows and Linux (with sun jdk 1.4.2.).
> For windows, I had to update the masters for these tests, but running them on
> Linux still failed for me.
> With jdk131, ibm131 and ibm142 the LocalizedDisplay.sql test hung, and
> LocalizedConnectionAttribute exits with a MalformedInputException.
> It would be nice if we could figure out a way to add these tests to the
> suites...
> --- stack of LocalizedConnectionAttribute on Linux ---
> Exception in thread "main" sun.io.MalformedInputException
> at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java(Compiled Code))
> at
> sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
> at
> sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
> at java.io.InputStreamReader.read(InputStreamReader.java:208)
> at java.io.BufferedReader.fill(BufferedReader.java:153)
> at java.io.BufferedReader.readLine(BufferedReader.java:316)
> at java.io.BufferedReader.readLine(BufferedReader.java:379)
> at
> org.apache.derbyTesting.functionTests.harness.RunTest.setDirectories(RunTest.java:729)
> at
> org.apache.derbyTesting.functionTests.harness.RunTest.main(RunTest.java:262)
> ----------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
