[jira] [Created] (ISIS-2039) Redesign of Configuration

[Andi Huber (JIRA)]

Andi Huber created ISIS-2039:
--------------------------------

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2039:
-----------------------------
Description:
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

was:
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 text-file, which can be edited offline and reused as we do with layouts

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

[ 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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: reduce visibility of some config classes

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: simplify config access

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: cleaning up the component-provider mess

for web-modules: no longer negotiate by writing attributes to the
servlet-context, instead use a java class for that

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: fixing some tests

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: lazy binding to config for wicket

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: simplify config access

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: fixing some tests

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: lazy binding to config for wicket

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: removing arguments of @PostConstruct methods

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: removing arguments of @PostConstruct methods

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: reduce visibility of some config classes

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

Post by Andi Huber (JIRA)
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
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)

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: cleaning up the component-provider mess

for web-modules: no longer negotiate by writing attributes to the
servlet-context, instead use a java class for that

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

Post by Andi Huber (JIRA)
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
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)

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2039:
-----------------------------
Description:
Goals:

1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder

A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.

Side-effects ...

1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
3) removal of @PostConstruct methods that take arguments
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: proposed test fix

also cleaning up verbose tests

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: proposed test fix

also cleaning up verbose tests

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: more test fixes

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: more test fixes

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: experimenting with AppConfig managed by Guice

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: experimenting with AppConfig managed by Guice

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: solving the AppManifest lookup problem independently of the
configuration bootstrapping

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: solving the AppManifest lookup problem independently of the
configuration bootstrapping

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: moving type discovery to an earlier stage in bootstrapping

Integration Test Bootstrapping works.

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: simplify helloworld

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: moving type discovery to an earlier stage in bootstrapping

Integration Test Bootstrapping works.

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: simplify helloworld

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: on web-context: move the config bootstrapping from wicket
module to the main ServletContextListener

such that the wicket module is no longer responsible for initiating the
framework

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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

[ASF subversion and git services (JIRA)]

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

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

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

ISIS-2039: on web-context: move the config bootstrapping from wicket
module to the main ServletContextListener

such that the wicket module is no longer responsible for initiating the
framework

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

Post by Andi Huber (JIRA)
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
1) the framework shall provide a singleton instance of IsisConfiguration, which is an interface that provides immutable/readonly access to the config key/value pairs
2) the framework provides IsisConfigurationBuilder once during the early-bootstrap phase for r/w access to the config key/value pairs
3) first time any module requests access to IsisConfiguration, a singleton instance IsisConfiguration is built using the builder and the builder itself is no longer valid, meaning the framework denies any caller access to the builder
A benefit of this design is, that it is no longer required to pass around or hold instances of IsisConfiguration, because the framework provides a static means to get the current life-cycle's singletons for configuration.
Side-effects ...
1) cleanup and simplify bootstrapping code
2) no more configuration mocking for JUnit tests, instead use new internal Config API
4) removal of apache commons dependencies (really only required by the WebServer tool)

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