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

Simone Gianni resolved LABS-353.
--------------------------------

    Resolution: Fixed

> [beans] Make converters property aware
> --------------------------------------
>
>                 Key: LABS-353
>                 URL: https://issues.apache.org/jira/browse/LABS-353
>             Project: Labs
>          Issue Type: New Feature
>          Components: Magma
>    Affects Versions: Current
>            Reporter: Simone Gianni
>            Assignee: Simone Gianni
>             Fix For: Current
>
>
> Converters were born to be unaware that they are working on a specific 
> property, and this is fine.
> However, with LABS-351, now converters have a new role in the system, that is 
> not only to convert from one type to String, but also to convert it from some 
> intermediate "meta-types" to some generic final types, like byte[] or 
> streams. While the to-from String conversion can easily be handled without 
> knowledge of any other context, other conversions are not as simple.
> Moreover, such converters could assolve another function, that is to 
> "prepare" the data as required by the user. For example, issue LABS-213 is 
> about having forbidden elements in a rich text HTML be removed from the HTML 
> during the conversion phase. Another example could be the image converter to 
> resize images to conform to requirements, or to convert them to different 
> mime types than the one uploaded by the user.
> To do this, some converters requires access to the PropertyInfo object, where 
> validation and other informations are present.
> As a rule however, converters must keep working when they are used not in the 
> context of a property.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to