Hi, Starting another thread because the "Vote" that wasn't really an official vote at this point has outlived itself.
Without going into details about what each of the underlying mechanisms (DI, etc.) are there are two main categories of config solutions: 1. Annotated POJOS That includes the likes of Spring Config, Cfg4J or DeltaSpike. None of them has its own "Config" or "Configuration value holder. That's up to the application. You may find examples calling it AppConfig or e.g. Agorava uses DeltaSpike for OAuthAppSettings (backed by a simple properties file right now) 2. Value holder That includes Tamaya as of now, Typesafe Config or Apache Commons Config. None of the Tamaya proposal stated which of the two directions it shall use. The smaller the value holder gets, the more the question could arise what remains its purpose. I'm not suggesting either, just mention the two general directions. Regards, Werner
