> On 8 Dec 2016, at 07:22, David Holmes <david.hol...@oracle.com> wrote: > > On 8/12/2016 2:32 AM, Vincent Ryan wrote: >> A hexdump facility has been available for many, many years via an >> unsupported class: sun.misc.HexDumpEncoder. >> Although that class was always unsupported, it was still accessible. That >> accessibility changes with Jigsaw so I’m proposing >> a very simple replacement in a new and supported class: java.util.HexDump. >> >> Thanks. >> >> Bug: https://bugs.openjdk.java.net/browse/JDK-8170769 >> Webrev: http://cr.openjdk.java.net/~vinnie/8170769/webrev.00/ > > googling for "hexdump java" reveals quite a few hits - including > javax.xml.bind.DatatypeConverter.
DatatypeConverter is no longer directly accessible in JDK 9 as it is in the java.xml.bind module. So an ‘—add-modules’ flag would be required. > > Does this sun.* class really meet the acceptance criteria for inclusion in > java.util? That bar is intentionally set very high. We considered other locations for these methods (including java.lang.String !) but settled on java.util.HexString as a good balance between visibility and controversy. > > Just wondering ... > > David >
