You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tamaya.apache.org by "Oliver B. Fischer (JIRA)" <ji...@apache.org> on 2015/04/25 23:57:38 UTC

[jira] [Created] (TAMAYA-77) Clearify the usage of the ConfigurationContextBuilder

Oliver B. Fischer created TAMAYA-77:
---------------------------------------

             Summary: Clearify the usage of the ConfigurationContextBuilder
                 Key: TAMAYA-77
                 URL: https://issues.apache.org/jira/browse/TAMAYA-77
             Project: Tamaya
          Issue Type: Task
          Components: Core
    Affects Versions: 0.1-incubating
            Reporter: Oliver B. Fischer
             Fix For: 0.1-incubating


This issue is a reminder to discuss the usage of the ConfigururationContextBuilder.

While analyzing our service providers I recognized that the {{DefaultConfigurationContextBuilder}} is not treated like a service provider. Instead of accessing it via the usual SPI meachnism simply a new instance is created. Furthermore {{DefaultConfigurationContextBuilder}} is the  only implementation of {{ConfigurationContextBuilder}}.

We should discuss:
- could be there more than one implementation of {{ConfigurationContextBuilder}}?
- If no, can we remove the {{ConfigurationContextBuilder}} interface from our API?




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)