[
https://issues.apache.org/jira/browse/POLYGENE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896960#comment-15896960
]
Niclas Hedhman commented on POLYGENE-117:
-----------------------------------------
Thanks for the very explicit write-up.
I had in mind, that there was a ConfigurationService composite type, which the
Configuration would use to fetch the default configuration from, instead of
doing it so explicitly in the catch{} clauses.The default Mixin would do
something similar to what we do now, but with regular Mixin override in
bootstrap, users could extend this in a very simple fashion.
> Investigate "external" Configuration
> ------------------------------------
>
> Key: POLYGENE-117
> URL: https://issues.apache.org/jira/browse/POLYGENE-117
> Project: Polygene
> Issue Type: New Feature
> Reporter: Niclas Hedhman
>
> There is configuration and then there is configuration.
> The Polygene Configuration concept is primarily concerned over application
> internal details, and because of its ease-of-use, the larger picture is not
> in full view.
> In the enterprise, there are massive systems designed to externalize
> configuration from applications, and those applications often need to
> interface with those.
> We should investigate how these systems are typically built and organized,
> and see if we can make a reasonable abstraction, that ties into the
> Configuration concept in Polygene. Allowing Configuration to be backed by
> networked service(s) or even file system data.
> This may very well tie into the UnitOfWork-Services, that Kent has recently
> raised, and might therefor be dependent on the overhaul of the UoW definition.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
