-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
6
-
generic
-
generic
The Sun JDK/JRE 1.4.1 contains supports for character converters for a number of EBCDIC codepages. For example IBM-939 (Cp939). There are a whole number of 'recent' EBCDIC codepages that are not supported by JDK/JRE 1.4.1, for example IBM-280, IBM-1027, IBM-1047, IBM-1390, IBM-1399 to name but a few.
A Java application using the Sun JDK/JRE and communicating with an IBM Mainframe therefore cannot handle data sent to it in any of these new codepages.
Please note that this RFE is *not* addressed by the new SPI interface for charsets (and which was used as the justification for not providing support for IBM-1047 in RFE 411810) as this RFE requests support for these new charsets in Sun's JDK/JRE.
So,
1) Is there any chance of having support for these charsets and the other 'missing' ones incorporated please ?
2) Is it possible to have these supported using the new 'java.nio.charset' apis please ?
3) Ideally, it would also be good if there were a (non-heuristic) way of identifying a charset as being an EBCDIC charset using the nio apis.
More (Sun proprietary) justification can be found in the comments section
Thanks
Rob
A Java application using the Sun JDK/JRE and communicating with an IBM Mainframe therefore cannot handle data sent to it in any of these new codepages.
Please note that this RFE is *not* addressed by the new SPI interface for charsets (and which was used as the justification for not providing support for IBM-1047 in RFE 411810) as this RFE requests support for these new charsets in Sun's JDK/JRE.
So,
1) Is there any chance of having support for these charsets and the other 'missing' ones incorporated please ?
2) Is it possible to have these supported using the new 'java.nio.charset' apis please ?
3) Ideally, it would also be good if there were a (non-heuristic) way of identifying a charset as being an EBCDIC charset using the nio apis.
More (Sun proprietary) justification can be found in the comments section
Thanks
Rob