Short comments inline... 2016-07-15 16:28 GMT+02:00 Oliver B. Fischer <[email protected]>:
> Hi all, > > > Am 15.07.16 um 14:42 schrieb Anatole Tresch: > >> 1) Do we want to support non String values, including type literals? >> > Yes, we need this nowaday. String would work but would never consider a > framework nowadays where I have to do all this by hand. Other frameworks as > Spring supports this out of the box. > 2) Do we want to support mutability? OOTB as part of the Configuration >> interface, or indirectly, e.g. by applying some kind of Adapter pattern? >> > I will have to look at the API to answer this. > >> 3) Anything else? >> > Please do not start simply now two overhaul the whole core stuff. I try to > use Tamaya in my projects to get a feeling how it feels to use Tamaya. > Changing the API now would be not helpful for me at least. > - > That was not my intention. I dont think we need more basically, but I am open to hear argument, if I should have overseen something... > > I will have time to help again with the implementation. I think Phil and >> Oliver are also motivated, if we we see a good chance to progress with our >> initiative... ;) So would be great if the other guys could at least join >> discussions here on the list and actively help directing us to do the >> right >> things... >> > > Yes, but we need a better process to define our goals. > -> And a clear timeline! > One thing I'd love once the API will be reviewed is to provide a simple >>> tomee-embedded-tamaya-server fatjar providing a REST application and a >>> client "source" to fill the config entries. We would then have a >>> fullstack >>> solution ready to use. >>> >> - > Sounds good! -- *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*
