JDK-4710890 : native2ascii couldn't write content to existed file on windows
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio.charsets
  • Affected Version: 1.4.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: sparc
  • Submitted: 2002-07-04
  • Updated: 2002-11-07
  • Resolved: 2002-11-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Description
hopper b16,
windows2000 sch

reproduce:
in windows cmd shell, run it with two times:
c:\tmp> native2ascii <any native file> 1.txt

will get the information:
java.lang.Exception: 1.txt could not be written.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b07
2004-06-14

EVALUATION Bug determined to exist on win32 systems only. See Workaround description. Fix in progress for 1.4.2 ###@###.### 2002-08-02
2002-08-02

WORK AROUND If run within shell environment (eg CygWin or MKS) write a shell wrapper for native2ascii which determines if output filename already exists and is writeable. The script should remove the output file if both conditions are met before invoking the 1.4.1 native2ascii executable with the supplied args. ###@###.### 2002-08-02
2002-08-02