Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Sat, 15 Sep 2012 07:23:10 +1100 (NCT)
From: "Gary D. Gregory (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <1789796682.82147.1347654190207.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1997434221.18637.1333650750424.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (CODEC-139) DigestUtils: add updateDigest methods
 and make methods public.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CODEC-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary D. Gregory closed CODEC-139.
---------------------------------


Released in 1.7 today.
                
> DigestUtils: add updateDigest methods and make methods public.
> --------------------------------------------------------------
>
>                 Key: CODEC-139
>                 URL: https://issues.apache.org/jira/browse/CODEC-139
>             Project: Commons Codec
>          Issue Type: Improvement
>            Reporter: Sebastien Dubois
>            Priority: Trivial
>              Labels: patch
>             Fix For: 1.7
>
>         Attachments: DigestUtils-patch.txt, DigestUtils-patch-updated-2012-04-20.txt, guavacourt-hooke1-qrcode-SMALL.png, guavacourt-psychicr-qrcode-SMALL.png
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> I've slightly modified the DigestUtils class:
> - changed the visibility (protected --> public) of a few methods: these methods are generally useful if one just wants to get a MessageDigest instance for a given algorithm
> - added two 'updateDigest' methods which can be used to add more data to digest to the provided MessageDigest. The advantage for the one that accepts a String argument is that it keeps the same logic as the rest of DigestUtils (uses getBytesUtf8). The second one which accepts a byte array is there for consistency

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira