The simple (but useful) samples you can find here illustrate the usage of [ini4j]. These are small, independent programs that may be translates and run. The build process of [ini4j] guarantees translatability and runability, since no distribution may be created without translating and running these programs. That's why these sources are not inserted into the document but can be found in separate .java files. But don't worry - your browser has a Back button, don't be afraid to use it :-)
The sample programs expect the .ini file as a command line argument. If there is no such argument, they use the sample.ini file.
The samples below use the standard JDK Preferences API, so there's no need for any special [ini4j] API knowledge to understand them.
The [ini4j] library has a simple API: the .ini file is a map of sections, while the section is a map of options. Due to the Java 1.5 generics these are type safe maps.
Yes, it can be done! To access the contents of sections you can use any of your self-defined Java Beans compatible API. In order to do this you have to create a Java Beans-style interface, and a wrapper object that executes it will be generated by the [ini4j] library around the section.