You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tamaya.apache.org by "Anatole Tresch (JIRA)" <ji...@apache.org> on 2014/12/12 14:09:13 UTC

[jira] [Assigned] (TAMAYA-22) Do we really need ConfigOperator?

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

Anatole Tresch reassigned TAMAYA-22:
------------------------------------

    Assignee: Anatole Tresch

> Do we really need ConfigOperator?
> ---------------------------------
>
>                 Key: TAMAYA-22
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-22
>             Project: Tamaya
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.1-incubating
>            Reporter: Werner Keil
>            Assignee: Anatole Tresch
>              Labels: api-change, design
>
> As of now using Lambdas (since {{@FunctionalInterface}} and similar types are heavily used) limit the minimal Java version for Tamaya to SE 8. 
> Unless this was to change, the {{ConfigOperator}} interface seems rather redundant. Using {{UnaryOperator<Configuration>}} instead would simplify the API and make it even more Lambda-friendly.



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