views:

3911

answers:

5

I want to create an ini file to store some settings for my application. Is it a good idea to find where the jar file is located and create an ini file there? If yes, then how can I find the location of the jar file?

But if you know a better solution for something like this, I would like to hear some of them.

EDIT: I'm using mac and I want to run the same application in windows. I could write something in the System.getProperty("user.home") directory, but I want to keep the system clean, if the user decides to remove the app. There is no a better way to store the settings file, for example in the same directory with the application?

A: 

You should not be storing temp files in the install directory of an application. Remember, the user running the application may not have write access to that directory. The safest place to put stuff like that is in C:\Documents and Settings\username\Application Data\ApplicationName folder (adjusting the name as necessary).

That said, however, I would probably store that type of stuff in the registry instead of a file on their computer. (But, that's just me.)

BoltBait
and what about running the same application in MacOS?? And I totally agree with this article.. http://www.codinghorror.com/blog/archives/000939.html So I think registry is not a good idea at all :)
Lipis
A: 

It depends whether your ini needs to be human readable/writable under normal circumstances. If not, you can use a properties file rather than an ini file, and store it in the "user" directory.

As for finding the jar file, you would have to find the ClassLoader for a class known to be loaded from the jar, check that it was the appropriate type of ClassLoader (ie that it's really been loaded from a jar), and you can extract the path from that. I can probably dig out the code to do this if that's really what you want. I wouldn't necessarily recommend it.

EDIT The user.home property will give you the user directory, which you can safely use.

Draemon
user.dir gives you the current working dir, which may not be safe or appropriate. user.home gives you the user's home directory.
Chris Boran
Is it safe to assume the 'user.home' property gives you an appropriate value for each environment? That is, /home/{user} on *nix, the relevant Documents and Settings subdirectory for Windows, etc?
Andrew
That's what 'user.home' is supposed to do.
Martin Klinke
oops - yes, clearly I meant user.home (edited to avoid misdirection)
Draemon
A: 

Typically Java programmers don't use .ini files, but .properties files (different format). You can use the java.lang.Properties class as a nice programmatic wrapper if you do.

While you can get the location of your jar file by calling getProtectionDomain().getCodeSource().getLocation() on your class's .class member, I do not recommend that you do this.

I would instead write the file to the System.getProperty("user.home") directory - the users' home directory, or if it is truly temporary, System.getProperty("java.io.tmpdir")

Chris Boran
Hmm... I am a noob in Java, so yes .properties is a better idea. But where do you store your settings, when you are writing an application in Java. I'm using mac, but I want to run it in a windows environment as well.
Lipis
+7  A: 

You can locate your application directory using the ClassLoader. See: Java: finding the application directory. Rather than an .INI file, use a .properties file - you can load and save this via the Properties class.

As others have noted, you should not write user settings to your application directory. What if the user does not have write access to the application directory? What if your application is being used by multiple users on the same system at the same time? Neither of these situations are unusual, even on Windows.

You might still want to load some settings from the application directory - perhaps the administrator has configured default settings there.

A common convention is to save user settings to the user's home directory:

/home/user/.eclipse
C:\Documents and Settings\User\.eclipse

Although this means you might leave stray files behind, this can be beneficial if the user re-installs the app. Document such things in a README. Here is how to create and get a reference to the directory:

public static File getSettingsDirectory() {
    String userHome = System.getProperty("user.home");
    if(userHome == null) {
        throw new IllegalStateException("user.home==null");
    }
    File home = new File(userHome);
    File settingsDirectory = new File(home, ".myappdir");
    if(!settingsDirectory.exists()) {
        if(!settingsDirectory.mkdir()) {
            throw new IllegalStateException(settingsDirectory.toString());
        }
    }
    return settingsDirectory;
}

On unix-like operating systems, starting the directory name with a period (".myappdir") will make the directory hidden. On Windows, it will be located below My Documents, so users will not see the directory unless they go looking for it.

McDowell
+2  A: 

If the settings are only written by your application (rather than edited manually), consider using the Preferences API.

Dan Dyer