Bug ID: JDK-4952580 Convert use of old sun.io APIs into new java.nio.charset APIs

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.

Other
5.0 b32Fixed

In Mustang, we plan to remove sun.io.  The contents of this internal API have
been deprecated in favor of java.nio.charset which was introduced in Merlin.
As of Tiger, the old sun.io converters redirect to the new API.  Use of
the old converters will result in a deprecation warning at compile time.

The following list of files from the j2se workspace have been identified as
depending on sun.io:

  src/share/classes/com/sun/org/apache/xml/internal/serialize/EncodingInfo.java
  src/share/classes/com/sun/org/apache/xml/internal/serializer/Encodings.java
  src/share/classes/com/sun/org/apache/xml/internal/serializer/ToStream.java

These files are new to Tiger.  If the dependency is mostly superficial, we
would suggest that it be removed before Tiger ships.

These files (and any others which use sun.io) need to be converted to use the
new java.nio APIs by feature freeze of Mustang (at the very latest).  Ideally,
we would encourage people to schedule this work for completion in Dragonfly so
that sun.io can be removed before we start shipping Mustang CAP builds or
delivering to Solaris.

-- iag@sfbay 2003-11-11

Relates :	JDK-4948149 - (cs) deprecate old sun.io converters
Relates :	JDK-4454622 - (cs) Most character conversion clients do not use NIO API