Version 1.5.3 of Bee Config is now available. This brings JavaBean integration, a new feature for those who would like easy configuration files combined with pojos with typed properties.
The new feature allows you to load your Config from a file (or wherever) as normal, then use it to populate JavaBeans, which may themselves contain further JavaBeans. You can create your own JavaBean and pass it in. Or you can specify the class of the bean and it will be created reflectively for you.
Three styles of JavaBean are supported:
Plain old JavaBeans with getters and setters for their fields. Typically, these have a no-argument constructor too.
Immutable JavaBeans with getters for their fields. A constructor is required that has arguments to match the fields. There are of course no setters.
Immutable JavaBeans without getters, but with simple public fields instead. A constructor is required that has arguments to match the fields. There are of course no setters.
Bee Config supports nested configurations, a feature that has been part of the API for a long time. The ability to nest sections and subsections it also of benefit when applying some of the values to JavaBeans, especially if any of the fields are themselves JavaBeans that need to be populated recursively. This is fully supported now.