commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (Commented) (JIRA)" <>
Subject [jira] [Commented] (LANG-778) Add UUIDUtils.toByteArray and UUIDUtils.fromByteArray
Date Wed, 23 Nov 2011 15:07:40 GMT


Joerg Schaible commented on LANG-778:

bq: BTW, why did you decide to use high byte first?

This is what I said: The UUID is *defined* as sequence of 16 bytes together with a String
representation. There's no endian stuff involved. It's just that the UUID Java implementation
provides access to the single bits using two long values, which should be a lot faster than
an indirection using String. The Java runtime developers did use big endian as natural choice
of the JVM default.

So, the endian problem does not affect the proposed UUIDUtils, but for something like ByteUtils
this might be different. One solution is to document that this class expects big endian and
that EndianUtils can be used otherwise.
> Add UUIDUtils.toByteArray and UUIDUtils.fromByteArray
> -----------------------------------------------------
>                 Key: LANG-778
>                 URL:
>             Project: Commons Lang
>          Issue Type: New Feature
>          Components: lang.*
>            Reporter: Joerg Schaible
>            Assignee: Joerg Schaible
>            Priority: Minor
>         Attachments: LANG-778.diff
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> A UUID represents 16 bytes. In some situation (e.g. using DBs that do not have native
support for the type UUID) it is necessary to use directly the bytes. The JDK does not support
the transformation from UUID to bytes and back, therefore I'd like to add UUIDUtils with the
two proposed methods.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message