store all the details in a class implementing Serializable interface..then save it in the file system..when the program starts you can initialize the class directly from the file. Read More
@cool_zephyr I will say it is everyone personal opinion/preference how to proceed. Because as to your recommendation I can say "why to bother with file read/write logic when there is already database connectivity?" @CoilFyzx it is difficult to give deceisive answer without knowing more about functionality of your application. 1st … Read More
To save data locally, why not look at something like the embeddable H2 database from http://www.h2database.com/html/main.html - it is a brilliant, small SQL database, written in pure Java. As for the last view, you can easily serialize and deserialize the state of your application, if your design supports it, of … Read More
In defence of cool_zephy's suggestion... Storing a Serializable object - no matter how complex its internal structure and content - is a single call to writeObject. Restoring it ditto. Storing/restoring data with multiple occurences of complex data by mapping it into relational tables can be very complex and code intensive. … Read More
Serialization allowes you to write/read arbitrary objects to a binary file, in a Java-specific binary format that may be subject to change (not just an empty threat - I had a live system fail when the serialisation of Image objects changed somewhere in the later releases of 1.6). A very … Read More
Edited by CoilFyzx: Realized that my previous statements sounded a bit ambiguous.
Edited by JamesCherrill