[
https://issues.apache.org/jira/browse/POLYGENE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated POLYGENE-117:
------------------------------------
Description:
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.
was:
There is configuration and then there is configuration.
The Zest 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 Zest. 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.
> 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)
