polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POLYGENE-97) UnitOfWork as a Composite
Date Sat, 18 Feb 2017 02:40:44 GMT

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

Niclas Hedhman commented on POLYGENE-97:
----------------------------------------

Since the UnitOfWorkFactory is now a Service, doesn't that mean that UnitOfWork can be of
any type whatsoever?

> UnitOfWork as a Composite
> -------------------------
>
>                 Key: POLYGENE-97
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-97
>             Project: Polygene
>          Issue Type: Sub-task
>            Reporter: Niclas Hedhman
>             Fix For: 3.0
>
>
> Perhaps it is possible to refactor the UnitOfWork(Factory) in such a way that it is a
Composite and can be custom modeled with Concerns, Mixins and other fragments.
> If possible many things would become easier, StateNotificationListener becomes a SideEffect,
which in turn could be asynchronous. Or Usecase could possibly be an annotation or metaInfo
on the UoW in each module.
> It might also lead to a different delegation between UnitOfWork and EntityStore, and
possibly more than one UnitOfWork implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message