Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Fri, 31 Jul 2015 17:32:04 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12850652.1438363910000.341784.1438363924518@Atlassian.JIRA>
In-Reply-To: <JIRA.12850652.1438363910000@Atlassian.JIRA>
References: <JIRA.12850652.1438363910000@Atlassian.JIRA>
 <JIRA.12850652.1438363910605@arcas>
Subject: [jira] [Created] (ZEST-110) Allow Composite state to be backed by
 Spring Beans.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Niclas Hedhman created ZEST-110:
-----------------------------------

             Summary: Allow Composite state to be backed by Spring Beans.
                 Key: ZEST-110
                 URL: https://issues.apache.org/jira/browse/ZEST-110
             Project: Zest
          Issue Type: New Feature
            Reporter: Niclas Hedhman


State is managed through the @State annotation and the StateHolder and AssociationStateHolder.

Since we now support dynamic replacement of Mixins during bootstrap, it would be relatively easy to replace PropertyMixin (et al) as the implementation for Property<?>, and we should allow a mechanism where Spring Beans can do the backing instead.

This could in many cases simplify the integration with Spring-centric applications, and easier to transition from a Spring oriented world to the goodies of Zest.

With additional thinking, this could possibly also be the route to ORM support in persistence.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)