[jira] [Created] (TAMAYA-236) Reconsider PropertySource ordering and getOrdinal()

["Werner Keil (JIRA)" <ji...@apache.org>]

Werner Keil created TAMAYA-236:
----------------------------------

             Summary: Reconsider PropertySource ordering and getOrdinal()
                 Key: TAMAYA-236
                 URL: https://issues.apache.org/jira/browse/TAMAYA-236
             Project: Tamaya
          Issue Type: Improvement
          Components: API
    Affects Versions: 0.2-incubating
            Reporter: Werner Keil
             Fix For: 0.3-incubating


As marked {TODO rethink whole default PropertySources and ordering} in {PropertySource} we should reconsider the whole {getOrdinal()} method.

The Chief Architect of Lightbend (formerly Typesafe), the key contributor to Typesafe Config mentioned in a Microprofile discussion about ordinals, that he's 
>unconvinced that the use of ordinals is a preferred solution for the problem >at hand—it just ends up becoming magic numbers which sadly are not >absolutely ordered. It is also extremely finicky since a change in an ordinal >by a third party will lead to surprising effects downstream, most specifically >for config value overloads.
>A deterministic, absolute, order at declaration site means that the >consumer is always in control and order cannot change due to the whims >of third-party libraries.

We may take a look at how e.g. Typesafe Config (and others like Apache Commons Config) handle this, but I am not aware either of them use the concept of an "ordinal" or "order" to solve this problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [jira] [Created] (TAMAYA-236) Reconsider PropertySource ordering and getOrdinal()

[Werner Keil <we...@gmail.com>]

As mentioned to Anatole, maybe although I could be unable to join the call
or speak (another dentist appointment) I created this ticket to discuss the
ordinal question.

Backed by a rather clear and critical (of the ordinal concept) statement by
Lightbend Chief Architect and Deputy CTO Victor Klang in a Microprofile
discussion thread. Given the relevance of Typesafe Config probably even
more than Akka or other new fancy Microservice technologies offered by
Lightbend, I'd say, he or maybe people at Pivotal know more about that
because their frameworks are real and used by a large number of people or
other projects (also looking at downstream dependencies). These are giants
in their field, DeltaSpike isn't even used for configuration in many cases,
because it does "everything and nothing". While these other frameworks and
distinct modules were created for configuration alone.

Werner


On Thu, Feb 2, 2017 at 7:50 PM, Werner Keil (JIRA) <ji...@apache.org> wrote:

> Werner Keil created TAMAYA-236:
> ----------------------------------
>
>              Summary: Reconsider PropertySource ordering and getOrdinal()
>                  Key: TAMAYA-236
>                  URL: https://issues.apache.org/jira/browse/TAMAYA-236
>              Project: Tamaya
>           Issue Type: Improvement
>           Components: API
>     Affects Versions: 0.2-incubating
>             Reporter: Werner Keil
>              Fix For: 0.3-incubating
>
>
> As marked {TODO rethink whole default PropertySources and ordering} in
> {PropertySource} we should reconsider the whole {getOrdinal()} method.
>
> The Chief Architect of Lightbend (formerly Typesafe), the key contributor
> to Typesafe Config mentioned in a Microprofile discussion about ordinals,
> that he's
> >unconvinced that the use of ordinals is a preferred solution for the
> problem >at hand—it just ends up becoming magic numbers which sadly are not
> >absolutely ordered. It is also extremely finicky since a change in an
> ordinal >by a third party will lead to surprising effects downstream, most
> specifically >for config value overloads.
> >A deterministic, absolute, order at declaration site means that the
> >consumer is always in control and order cannot change due to the whims >of
> third-party libraries.
>
> We may take a look at how e.g. Typesafe Config (and others like Apache
> Commons Config) handle this, but I am not aware either of them use the
> concept of an "ordinal" or "order" to solve this problem.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
>