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 2015/10/30 11:05:27 UTC

[jira] [Resolved] (TAMAYA-128) Adding ConversionContext to converter params

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

Anatole Tresch resolved TAMAYA-128.
-----------------------------------
    Resolution: Implemented

> Adding ConversionContext to converter params
> --------------------------------------------
>
>                 Key: TAMAYA-128
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-128
>             Project: Tamaya
>          Issue Type: New Feature
>          Components: API
>    Affects Versions: 0.1-incubating
>            Reporter: Anatole Tresch
>            Assignee: Anatole Tresch
>             Fix For: 0.2-incubating
>
>
> For passing metadata to a PropertyConverter more arguments are needed then only the simple String input value. Therefore an additional ConversionContext is passed with the following data:
> * the requested key
> * the requested target type
> * the base configuration
> * the injected field or method (optional).
> * a (mutable) list of supported formats as Strings
> The ladder also provides an elegant way to enable converters to dynamically register their supported formats, making them available for improved user feedback on the currently supported formats for a type. Nevertheless the PropertyConverter interface can stay functional.
> *Unfortunately this change breaks the current PropertyConverter SPI*, but extending the ConversionContext should be possible when needed in the future without breaking the API again.



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