commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRYPTO-75) ConfigurationKeys#COMMONS_CRYPTO_CIPHER_CLASSES_DEFAULT is not guaranteed constant
Date Fri, 17 Jun 2016 16:27:05 GMT

    [ https://issues.apache.org/jira/browse/CRYPTO-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336393#comment-15336393
] 

Benedikt Ritter commented on CRYPTO-75:
---------------------------------------

Can you provide an example how that code would look like? We should not over complicate things.
We already have that nasty code that handles the sun.nio.Buffer calls.

> ConfigurationKeys#COMMONS_CRYPTO_CIPHER_CLASSES_DEFAULT is not guaranteed constant
> ----------------------------------------------------------------------------------
>
>                 Key: CRYPTO-75
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-75
>             Project: Commons Crypto
>          Issue Type: Bug
>            Reporter: Sebb
>
> ConfigurationKeys#COMMONS_CRYPTO_CIPHER_CLASSES_DEFAULT contains a fully-qualified class
name.
> This is not guaranteed to be constant if the package names ever have to be changed.
> The constant should be changed to an alias that is handled by the runtime code when creating
the class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message