Bug ID: JDK-4454622 (cs) Most character conversion clients do not use NIO API

Versions (Unresolved/Resolved/Fixed)

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.

JDK 6
6 b27Fixed


Name: nl37777			Date: 05/04/2001

Of the various subsystems in the J2SDK that use character
conversion, only a few have been changed to use the NIO APIs. As a
result, character converters plugged into the NIO SPI cannot be relied
on to be used by the entire J2SDK.

As of build 63 (5/2/01), the situation was as follows:

Using java.nio API exclusively:
java.nio.Channels

Using both java.nio and sun.io interfaces:
java.io.InputStreamReader
java.io.OutputStreamWriter
java.lang.StringCoding (for java.lang.String)
sun.awt.datatransfer.DataTransferer
sun.tools.native2ascii.Main

Using sun.io interfaces exclusively:
com.sun.corba.se.internal.core.CodeSetConversion
sun.awt.FontDescriptor
sun.awt.PlatformFont
sun.awt.motif.MFontPeer
sun.awt.windows.WDefaultFontCharset
sun.awt.windows.WFontPeer
sun.io.CompoundTextSupport
sun.jdbc.odbc.JdbcOdbcObject
sun.jdbc.odbc.JdbcOdbcResultSet
sun.jdbc.odbc.JdbcOdbcPreparedStatement
sun.net.NetworkClient
sun.plugin.navig.motif.PluginPSPrintStream
sun.print.PSPrinterJob
src/share/native/sun/awt/font/fontmanager/fontobjects/cmaps.cpp
src/share/native/sun/awt/font/fontmanager/fontobjects/fontObject.cpp
src/solaris/native/sun/awt/awt_Font.c
src/solaris/native/sun/awt/font/nrScalerContext.cpp
src/win32/native/sun/windows/awt_Font.cpp
======================================================================

EVALUATION We plan to complete the migration to the new character converters in Tiger. -- iag@sfbay 2002-05-15 The sun.io converters will be removed from Mustang. For Tiger, use of these converters will result in a compile-time deprecation warning. See bug 4948149. We do not recommend further use of the sun.io converters. -- iag@sfbay 2003-11-03 Since there are separate bugids for jdbc, Dnd, i18n/awt/2d related sun.io changes, this bugid is now used to trace the change needed in TL area only. Currently there are only 3 files left java/lang/StringCoding.java sun/nio/cs/StreamEncoder.java sun/nio/cs/StreamDecoder.java which include the code to fallback to sun.io converters. ###@###.### 2005-2-15 21:36:44 GMT

15-02-2005

WORK AROUND Name: nl37777 Date: 05/04/2001 ======================================================================

02-09-2004

Relates :	JDK-4948142 - Handler and XMLFormatter should not call old sun.io apis
Relates :	JDK-4887597 - remove uses of sun.io in sun.tools.*
Relates :	JDK-4952584 - Convert use of old sun.io APIs into new java.nio.charset APIs
Relates :	JDK-4948136 - Scanner.create should call Charset.default() instead of sun.io api
Relates :	JDK-4952580 - Convert use of old sun.io APIs into new java.nio.charset APIs
Relates :	JDK-4948149 - (cs) deprecate old sun.io converters
Relates :	JDK-4772857 - (cs) Need a standard way to get the default encoding
Relates :	JDK-4952588 - Convert use of old sun.io APIs into new java.nio.charset APIs
Relates :	JDK-6228568 - (cs) Charset.forName() throws inaccurate/inappropriate exception when null is the charset name
Relates :	JDK-4952578 - Convert use of old sun.io APIs into new java.nio.charset APIs
Relates :	JDK-6275382 - Rowset2.0: no db2 test run due to some classes under sun/io/ missing. needed a new jdbc driver
Relates :	JDK-4954012 - Convert use of old sun.io APIs into new java.nio.charset APIs
Relates :	JDK-4952586 - Convert use of old sun.io APIs into new java.nio.charset APIs