[jira] [Resolved] (POLYGENE-97) UnitOfWork as a Composite

["Niclas Hedhman (JIRA)" <ji...@apache.org>]

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

Niclas Hedhman resolved POLYGENE-97.
------------------------------------
    Resolution: Fixed

This was implemented more than a year ago.

The UnitOfWork is instantiated as a TransientComposite in the default UnitOfWorkFactory, and could be given additional concerns and sideeffects.


> 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
>            Assignee: 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)