Actually I found the commit removing the module: https://github.com/apache/incubator-tamaya-extensions/commit/dc75aa44871c43fe6c942bb3c629b48813e7d173
2017-09-21 17:40 GMT+02:00 Anatole Tresch <[email protected]>: > Hi Christian > > actually I am confused myself now. It seems that the collections module is > somehow disapeared. That definitively happened when our repos were > reorganized, accidently, I assume. So I will check the history and readd it > to the sandbox first. > > What is always an option is to write and register a *PropertyConverter* > on your own that converts from *String* to *List.class* for example. When > accessing a configuration value, you can explicitly pass the target type as > *List*, so your converter will then be selected. > In case you want to collect entries from different sources (instead of > overriding, which is the default), you can also register a custom > *PropertyValueCombinationPolicy* to provide e.g. the possibitliy to > combine value from different sources (e.g. into a comma separated list) > before they are passed to the converter. > This is what the collections module basically did, based on additional > meta-entries provided... > > Basically for a generic solution Tamaya must given knowledge, which > entries are to be managed as collections. > This was done by adding additional meta-entries, with special syntax. > Additionally some syntax must be defined, how collection typed values are > modelled as Strings. > > I will come back to this later, when the module is restored. This will > help to explain the concepts more easily. > > Stay tuned. > J Anatole > > > > 2017-09-21 14:29 GMT+02:00 Niehues, Christian <Christian.Niehues@its- > digital.de>: > >> Hi Anatole, >> >> >> like I already said in another email I started to switch my >> commons-configuration based configuration from a JBoss installation to a >> tamaya based configuration on Karaf. So I am still at the very first start, >> trying to load and provide different configuration files (xml, properties) >> from different locations (inside bundles, karaf etc folder). >> First I didn't saw that there is a apache-commons bundle at sandbox that >> may help so I tried to write my own PropertySource generating a commons >> configuration and converting the Properties to PropertyValues. To provide >> collections I also started to use tamaya-collections (btw: this is also not >> in sandbox). Now I saw that there is a apache-commons module in sandbox and >> try to use it but I don't know how much features it provides. >> >> So at the start its quiet hard to identify what features are supported by >> default modules or are available as extension and how well they are >> implemented or where I have to write my own extensions. But I hope I will >> get a better overview in the next days/weeks. >> >> Cheers, >> Christian >> >> >> ________________________________ >> Von: Anatole Tresch <[email protected]> >> Gesendet: Donnerstag, 21. September 2017 13:56:47 >> An: [email protected] >> Betreff: Re: [jira] [Created] (TAMAYA-306) tamaya-collections >> >> Hallo Christian >> >> thanks for your mail and happy to see, you used it. Unfortunately we moved >> it to the sandbox module in 0.3-incubating, since we thaught it is not >> yet >> mature enough. We may readd it in a later release, when we have some >> incidence that the API is working well. So, can you give us some more >> details, how you minly used it? Is there something we can improved on the >> module? Were you happy with it? How urgent you need it? >> Your input is very appreciated ;-) >> >> J Anatole >> >> >> 2017-09-21 13:14 GMT+02:00 Christian Niehues (JIRA) <[email protected]>: >> >> > Christian Niehues created TAMAYA-306: >> > ---------------------------------------- >> > >> > Summary: tamaya-collections >> > Key: TAMAYA-306 >> > URL: https://issues.apache.org/jira/browse/TAMAYA-306 >> > Project: Tamaya >> > Issue Type: Improvement >> > Components: Extensions >> > Affects Versions: 0.4-incubating >> > Reporter: Christian Niehues >> > Priority: Minor >> > >> > >> > I am confused about the status of the tamaya-collections extension. It >> > seems that the extension has been dropped because I can't see it in >> > 0.4-incubating, last available version is 0.2-incubating. I supposed it >> has >> > been integrated into core but can't either see indications for this. It >> > seems that it's working with 0.2-incubating but I think you should clear >> > this confusion. >> > >> > >> > >> > -- >> > This message was sent by Atlassian JIRA >> > (v6.4.14#64029) >> > >> >> >> >> -- >> *Anatole Tresch* >> PPMC Member Apache Tamaya >> JCP Star Spec Lead >> *Switzerland, Europe Zurich, GMT+1* >> *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> * >> [https://s0.wp.com/i/blank.jpg]<http://maketechsimple.wordpress.com/> >> >> Make Tech Simple | This is my personal blog on anything I want to share >> related to enterprise computing, especially related to Java, software >> design and architecture.<http://maketechsimple.wordpress.com/> >> maketechsimple.wordpress.com >> This is my personal blog on anything I want to share related to >> enterprise computing, especially related to Java, software design and >> architecture. >> >> >> >> *Twitter: @atsticks, @tamayaconf* >> >> *Speaking at:* >> >> [image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con] >> > > > > -- > *Anatole Tresch* > PPMC Member Apache Tamaya > JCP Star Spec Lead > *Switzerland, Europe Zurich, GMT+1* > *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> * > *Twitter: @atsticks, @tamayaconf* > > *Speaking at:* > > [image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con] > > -- *Anatole Tresch* PPMC Member Apache Tamaya JCP Star Spec Lead *Switzerland, Europe Zurich, GMT+1* *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> * *Twitter: @atsticks, @tamayaconf* *Speaking at:* [image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
