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] [Updated] (POLYGENE-110) Allow Composite state to be backed by Spring Beans.
Date Tue, 11 Apr 2017 07:16:41 GMT

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

Niclas Hedhman updated POLYGENE-110:
------------------------------------
    Description: 
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 Polygene.

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

  was:
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.


> Allow Composite state to be backed by Spring Beans.
> ---------------------------------------------------
>
>                 Key: POLYGENE-110
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-110
>             Project: Polygene
>          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 Polygene.
> With additional thinking, this could possibly also be the route to ORM support in persistence.



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

Mime
View raw message