|SettingStore vs java.util.preferences [message #1017313]
||Mon, 11 March 2013 15:01
|| John Gymer
Registered: November 2012
I have a need to store persistent (non-sensitive) data within my application, which shares a common source base for SWT, RAP and Tabris at present (with just a few differences between each).|
For SWT, it seems that using java.util.preferences is the way to go for this type of persistent data, storing local user settings and display preferences etc. This implementation internally will use Windows Registry, Mac .plist files and Linux properties/java files, which is fine - let the runtime handle it for me based on its platform and I'm happy!
However, when it comes to RAP, is java.util.preferences a good idea? Does it work on all AppServers (I'll be running my RAP/Tabris versions under a variety of appservers on a variety of platforms from Windows rights up to mainframe)?
Is the RWT SettingStore more appropriate, more reliable, or does SettingStore actually use java.util.preferences underneath for its default implementation?
Any useful comments and opinions most appreciated!
Just because you can doesn't mean you should
Powered by FUDForum
. Page generated in 0.01754 seconds