Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead | Eclipse UOMo Lead, Babel Language Champion | Apache Committer | Advisory Board Member, DWX '15
Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @DeviceMap | #EclipseUOMo | #DevOps Skype werner.keil | Google+ gplus.to/wernerkeil On Tue, Dec 23, 2014 at 11:04 AM, Romain Manni-Bucau <[email protected]> wrote: > > > > > > >> But it (DeltaSpike) is inheritly connected to CDI and > > > > That's just not true. And it's tried and used successfully in many big > projects (including my own which deals with 50 bn EUR, german stock > exchange, UK stock exchange, big swiss banks, etc). > > I'm not saying the DS api is the best, but it is able to do all that and > is 1/20th of the complexity and size of Tamaya right now. And still being > more powerful. > > > > It is Mark, at least in term of dependencies, I asked months ago to > explode core part but it was not the moment I guess ;) > > +1 Even projects deeply inherent to CDI like Agorava use just a few core modules of DeltaSpike but not config as of now. I am aware of the history of Commons Config, did use it in a few projects, but would not do it in many others. > > > >>> things not working out of the box: distributed configs > > > > For which distributed system? > > * Ehcache? > > > > * Terracotty? > > * Hadoop like clustering? > > * a simple shared file store? > > Where to put the meta-configuration for it? Where to define which one to > use? > > What fallback strategies to choose? > > > > > Never spoke of any technology. Spoke in term of use case: I have 5 > machines which need to read the same config. Constraint I'd like to > respet is: don't force a "complicated" config like hazelcast one for > instance. > > Let's not get me started on the Ehcache/JCache issue again;-) The Cache JSR (107) tried to abstract some of the configuration in ways one might even find to a small extent in more general purpose configuration APIs, but it got a rather weird notion and inheritance chain, not really intuitive, something that better not had been standardized in the first place, at least not for such a small niche. It does harm to the Java EE (8) ecosystem as a whole, since there's a large new room in the "Configuration Hell" already in place;-| Werner
