Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Sun, 12 Jul 2015 08:53:04 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12844420.1436691129000.164199.1436691184521@Atlassian.JIRA>
In-Reply-To: <JIRA.12844420.1436691129000@Atlassian.JIRA>
References: <JIRA.12844420.1436691129000@Atlassian.JIRA>
 <JIRA.12844420.1436691129629@arcas>
Subject: [jira] [Created] (ZEST-97) UnitOfWork as a Composite
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Niclas Hedhman created ZEST-97:
----------------------------------

             Summary: UnitOfWork as a Composite
                 Key: ZEST-97
                 URL: https://issues.apache.org/jira/browse/ZEST-97
             Project: Zest
          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.4#6332)