JDK-4625418 : RFE: LTP: java.beans.XMLEncoder should have an option to specify other charset than UTF-8
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 1.4.0,1.4.2,OpenJDK6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: linux,solaris_8,windows_nt
  • CPU: x86,sparc
  • Submitted: 2002-01-17
  • Updated: 2017-05-16
  • Resolved: 2011-03-08
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 7 Other
7 b07Fixed OpenJDK6Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Name: nt126004			Date: 01/17/2002


FULL PRODUCT VERSION :
java version "1.4.0-beta3"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta3-b84)
Java HotSpot(TM) Client VM (build 1.4.0-beta3-b84, mixed mode)


A DESCRIPTION OF THE PROBLEM :
XMLEncoder defaults to UTF-8 encoding
this is a problem when :
  - the "national" context uses accented character
  - we use the xml files for setting up tests
    and these files are modified/augmented
    in a human-readable way (using a text processor)
(and are later read using XMLDecoder)

 authorizing charset ISO-8859-1 will be a good
start ....
later when XML tools evolves may be we could go after other
 charsets ....

This bug can be reproduced always.
(Review ID: 138149) 
======================================================================

Comments
EVALUATION If user's documents should use specific encoding by contract we should allow him to create such documents.
08-11-2006

EVALUATION Name: nl37777 Date: 08/27/2004 I don't think this RFE is worth implementing. There are numerous text editors available that support UTF-8. Also, UTF-8 is the best choice for XML files, because according to the XML specification all XML processors must support UTF-8, while support for most other character encodings is optional (the other required XML encoding, UTF-16, is good for in-memory processing, but not well suited for files or network interchange). ======================================================================
28-08-2004