[
https://issues.apache.org/jira/browse/POLYGENE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962352#comment-15962352
]
Niclas Hedhman commented on POLYGENE-54:
----------------------------------------
A better idea; The converters are registered metaInfo on the Usecase of the
UnitOfWork. On top of that, I am adding an OPTIONAL UsecaseFactory, that if
present and visible to UnitOfWorkConcern (the concern that handles the
@UniitOfWorkPropagation), then the name of the usecase (from the annotation)
will be passed to the UsecaseFactory, and it can have arbitrary logic, caching
and so on for the Usecase, including the converters.
> Support more use-cases in toEntity/toValue mechanism
> ----------------------------------------------------
>
> Key: POLYGENE-54
> URL: https://issues.apache.org/jira/browse/POLYGENE-54
> Project: Polygene
> Issue Type: Bug
> Reporter: Paul Merlin
> Assignee: Niclas Hedhman
> Labels: unitofwork
> Fix For: 3.0
>
>
> See discussion at http://markmail.org/message/yqzezcovwieu6ev3
> Now deprecated Conversion Library has support for type-relaxed conversion
> plus a way to insert custom conversion code. New toEntity/toValue support in
> UnitOfWork don't.
> Some use-cases:
> - don't expose the whole state (eg. password hashes)
> - computed/transformed state (eg. entity state ~ value state)
> This issue is about finding additional solutions to support theses usecases
> in the toEntity/toValue mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
