[9] RFR 8170769: Provide a simple hexdump facility for binary data

Bernd Eckenfels ecki at zusammenkunft.net
Sat Dec 10 20:29:48 UTC 2016

i would agree that a hexdumper is too specific for java.base module.
But what about hex encoding and parsing (similiar to java.util.Base64. Since java.xml.bind is no longer in the base modules an alternative for DataTypeConverter in SE is missing.


On Sat, Dec 10, 2016 at 9:13 PM +0100, "Roger Riggs" <Roger.Riggs at oracle.com> wrote:

Hi Vinnie,

I think this doesn't belong in the java.base module;  it doesn't add 
enough value for a average developer
and it is not essential to the core.  I don't have another module 
suggestion but would suggest
looking elsewhere.

$.02, Roger

On 12/9/2016 8:02 PM, Vincent Ryan wrote:
> Thanks to those who provided review comments.
> I have incorporated most of them and updated the webrev:
>      http://cr.openjdk.java.net/~vinnie/8170769/webrev.01/
> The main changes are to tighten up the javadoc spec and to add three additional methods
> to support byte array ranges. The total number of public methods is now 7.
> I have not added support for InputStream or ByteBuffer. I think what we have in place is
> sufficient for now and HexDump can be enhanced later if there is demand.
> The other issue is related to streams implementation and I’d like to defer that until later.
> I think the API is in good shape now but please let me know if there are any must-fix API issues.
> Otherwise I will consider the API finalised and move this forward.
> Thanks.

More information about the core-libs-dev mailing list