[
https://issues.apache.org/jira/browse/TAMAYA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401607#comment-15401607
]
Mark Struberg edited comment on TAMAYA-169 at 8/1/16 7:17 AM:
--------------------------------------------------------------
Let's run down your questions:
* connecting to Consul or other popular config servers
Perfectly possible with my approach. Just provide a custom ConfigSourceProvider
who picks up the information from Consul (which is btw not a config server but
a service orchestration framework).
The bug is that the Tamaya API contains many additional concepts which blur the
line, are redundant and not clearly recognizable. E.g. ConfigQuery vs
ConfigOperator.
> Tamaya is a result of the JCP EC not finding enough working use cases for
> configuration
> to consider standardizing it when discussed by Anatole and others.
Txs, I was a very active part of it. Gerhard and I also had quite a few
personal meetings with Mike back then (starting as early as 2012 or 13).
If you check the posts from the google group from back then (
https://groups.google.com/forum/#!forum/java-config ) then you will see that
many of the technical discussion points are actually from me. So I'm not sure
what you like to tell us?
was (Author: struberg):
Let's run down your questions:
* connecting to Consol or other popular config servers
Perfectly possible with my approach. Just provide a custom ConfigSourceProvider
who picks up the information from Consul (which is btw not a config server but
a service orchestration framework).
The bug is that the Tamaya API contains many additional concepts which blur the
line, are redundant and not clearly recognizable. E.g. ConfigQuery vs
ConfigOperator.
> Tamaya is a result of the JCP EC not finding enough working use cases for
> configuration
> to consider standardizing it when discussed by Anatole and others.
Txs, I was a very active part of it. Gerhard and I also had quite a few
personal meetings with Mike back then (starting as early as 2012 or 13).
If you check the posts from the google group from back then (
https://groups.google.com/forum/#!forum/java-config ) then you will see that
many of the technical discussion points are actually from me. So I'm not sure
what you like to tell us?
> streamline the API and work towards a JSR proposal
> --------------------------------------------------
>
> Key: TAMAYA-169
> URL: https://issues.apache.org/jira/browse/TAMAYA-169
> Project: Tamaya
> Issue Type: Improvement
> Components: API
> Reporter: Mark Struberg
> Assignee: Mark Struberg
>
> The current Tamaya API is a tad too large to be easily understandable. It
> contains many nice features, but many of them are not core-features.
> I'd like to provide a very minimal set of absolutely necessary classes and
> interfaces.
> For a prototype see
> https://github.com/struberg/incubator-tamaya/tree/jsr-proposal/jsr/api/src/main/java/tamaya/config
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
