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

ASF subversion and git services commented on ISIS-2039:
-------------------------------------------------------

Commit d71acf3f3d95559bb0e3e2fe05e7aaba85c0ad25 in isis's branch 
refs/heads/2039-Redesign_of_Config from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=d71acf3 ]

ISIS-2039: major refactoring

move config code into its own module

remove number of classes in metamodel, that hold a reference to
IsisConfiguration or its implementation

hide the mutable IsisConfigurationDefault

Task-Url: https://issues.apache.org/jira/browse/ISIS-2039

> Redesign of Configuration
> -------------------------
>
>                 Key: ISIS-2039
>                 URL: https://issues.apache.org/jira/browse/ISIS-2039
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Goals (proposed):
> 1) decouple configuration from the rest of the framework infrastructure
> 2) remove the concept of framework internal configuration services
> 3) plan for supporting 'Spring Configuration' or 'MicroProfile Configuration 
> 1.1' via plugins
> 4) lets have immutable java data classes (config beans) to represent 
> configuration instead of key/value maps
> 5) when PROTOTYPING, allow for download of a configuration in serialized  
> form (text-file), which can be edited offline and reused as we do with layouts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to