You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/11/18 17:39:33 UTC

[jira] [Commented] (WICKET-5768) Improve class hierarchy of package org.apache.wicket.util.crypt

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

Martin Grigorov commented on WICKET-5768:
-----------------------------------------

Please develop this in a branch.

There is no any demand for these enhancements (no tickets, no requests in the mailing lists). I'd like to avoid making more API breaks for no good reason and release 7.0.0 sooner.

> Improve class hierarchy of package  org.apache.wicket.util.crypt
> ----------------------------------------------------------------
>
>                 Key: WICKET-5768
>                 URL: https://issues.apache.org/jira/browse/WICKET-5768
>             Project: Wicket
>          Issue Type: Improvement
>    Affects Versions: 7.0.0-M4
>            Reporter: Andrea Del Bene
>            Assignee: Andrea Del Bene
>            Priority: Minor
>             Fix For: 7.0.0-M5
>
>
> Following the work done for WICKET-5756, it would be nice to have a more flexible and clear hierarchy for cryptography classes in package org.apache.wicket.util.crypt. Currently we base our chipers on interface ICrypt which assumes we want to use a string as "secret" key.
> We can apply some refactoring to support keys of generic type and make the whole implementation more clear.



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