blocks|key|3149627|text|你可能想看看Resource+Bundles。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3149628|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.oracle.com/javase/7/docs/api/java/util/ResourceBundle.html^0|6|G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might want to look at <a href="https://docs.oracle.com/javase/7/docs/api/java/util/ResourceBundle.html" rel="nofollow noreferrer">Resource Bundles</a>.

blocks|key|361031|text|对于特定于用户的配置，您可以将配置文件写入"user.home“系统属性所指向的文件夹。当然只能在那台机器上工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361032|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For user specific config, you could write a config file to the folder pointed to by the "user.home" system property. Would only work on that machine of course.

blocks|key|3149666|text|这取决于您的J2SE应用程序类型：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3149667|主目录可执行JAR文件(非常简单)：使用user.home+System+property查找|offset|length|3149668|-J2SE。然后创建一个相应的子目录(比如PGP，SVN，...do)|unordered-list-item|3149669|Java+Web+Start为保护属性提供了非常好的包含方法。Always+user-specific|3149670|Finally+Eclipse+RCP:对于用户，您有工作区的概念(也是从user.home派生的)，对于computer+wide+usage|3149671|，您有配置(不完全确定如何在Vista中访问这些棘手的内容|3149672|所有这些方法在谨慎使用时都是操作系统中立的--使用正确的separatorChar。|3149673|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mindspring.com/~mgrand/java-system-properties.htm|1|http://java.sun.com/j2se/1.4.2/docs/api/java/io/File.html#separator^0|0|K|P|0|0|0|0|0|0|S|D|1|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|19|8|@]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

That depends on your kind of J2SE Application:

<ul>
<li>J2SE executable JAR file (very simple): use <a href="http://www.mindspring.com/~mgrand/java-system-properties.htm" rel="noreferrer">user.home System property</a> to find home-dir. Then make a subdir accordingly (like e.g. PGP, SVN, ... do)</li>
<li>Java Web Start provides very nice included methods to safe properties. Always user-specific</li>
<li>Finally Eclipse RCP: There you have the notion of the workspace (also derived from user.home) for users and configuration (not totally sure how to access that tricky in Vista) for computer wide usage</li>
</ul>

All these approaches are, when used with care -- use correct <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/io/File.html#separator" rel="noreferrer">separatorChar</a> -- OS neutral.

blocks|key|361044|text|Java有一个专门用java.util.prefs.Preferences编写的库。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|361045|Preferences+userPrefs+=+Preferences.getUserNodeForPackage(MyClass.class);+//+Gets+user+preferences+node+for+MyClass
Preferences+systemPrefs+=+Preferences.getSysteNodeForPackage(MyClass.class);+//+Gets+system+preferences+node+for+MyClass
Preferences+userPrefsRoot+=+Preferences.getUserRoot();+//+Gets+user+preferences+root+node
Preferences+systemPrefsRoot+=+Preferences.getSystemRoot();+//+Gets+system+preferences+root+node|code-block|syntax|javascript|361046|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/j2se/1.5.0/docs/api/java/util/prefs/Preferences.html^0|A|R|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Java has a library specifically for doing this in <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/prefs/Preferences.html" rel="noreferrer">java.util.prefs.Preferences</a>.

<pre><code>Preferences userPrefs = Preferences.getUserNodeForPackage(MyClass.class); // Gets user preferences node for MyClass
Preferences systemPrefs = Preferences.getSysteNodeForPackage(MyClass.class); // Gets system preferences node for MyClass
Preferences userPrefsRoot = Preferences.getUserRoot(); // Gets user preferences root node
Preferences systemPrefsRoot = Preferences.getSystemRoot(); // Gets system preferences root node
</code></pre>

blocks|key|3362576|text|首先是格式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3362577|3362578|Java+property+files很适合于键/值对(也可以自动处理换行符)。通过使用“点符号”，可以实现一定程度的结构。缺点是该结构不允许您轻松地枚举顶级配置实体并以向下钻取的方式工作。最适合用于一小部分特定于环境的设置--通常用于各种|ordered-list-item|offset|length|3362579|框架(特别是J2EE和|3362580|)的更复杂的配置。我建议你至少了解一下Spring+-即使你决定不使用它，它也包含了许多值得了解的想法。如果您决定使用自己的XML配置，我建议您使用带有定制序列化选项的XStream，或者如果您只需要解析一些XML，那么可以看看XOM。顺便说一句，Spring还允许插入定制的XML配置语言，但它是一个relatively+complex+task。XML配置最适合用于更复杂的“内部”配置，这些配置不会被end+user.|3362581|Serialized+Java对象看到或调整--这是一种保持对象状态并在以后恢复它的快速而简单的方法。如果您编写了一个配置GUI，并且您并不关心配置是否为人类可读的，那么它将非常有用。当你发展classes.|3362582|Preferences时，要当心compatibility+issues+-+Java+1.4中引入的，允许你在特定于平台的存储中存储类型文本、数字、字节数组和其他原语。在Windows上，这是注册表(您可以在HKLM或HKCU下的/Software/JavaSoft/Prefs之间进行选择)。在Unix下，同样的应用程序接口在用户主页或/etc下创建文件。每个首选项配置文件都可以导出和导入为XML文件。您可以通过将"java.util.prefs.PreferencesFactory“JVM属性设置为实现类名称来指定PreferencesFactory接口的自定义实现。|3362583|3362584|一般来说，根据您的应用程序场景，使用prefs+API可能是好事，也可能是坏事。|3362585|3362586|如果您计划在具有不同配置的同一台计算机上运行同一代码的多个版本，则使用首选项应用编程接口不是一个好主意。|3362587|如果您计划在受限环境(Windows域或严格管理的Unix计算机)中使用应用程序，则需要确保您具有对必要的注册表项/目录的正确访问权限。这不止一次让我大吃一惊。当不止一台活动机器被involved.|3362588|Preferences时，|3362589|要注意漫游配置文件(复制的主目录)，它们弥补了一些有趣的场景，并不像应用程序目录下的配置文件那么明显。大多数台式机支持人员都不希望也不喜欢它们。|3362590|3362591|关于prefs的文件布局，它再次取决于您的应用程序。一个通用的建议是：|3362592|3362593|将大多数XML文件打包到应用程序的JAR中，位于根目录或/META-INF目录下。这些文件将是只读的，并且被认为是$APP_HOME/+application.|3362594|Put下用户可修改配置的私有文件。它应该主要由属性文件组成，偶尔也包括一个简单的XML文件(XStream序列化)。这些文件作为安装过程的一部分进行了调整，并且通常不是用户应用程序，而是在点目录(即‘~/.myserviceable.|3362595|Under’)中存储任何用户配置的用户主页。用户配置可以覆盖应用程序配置目录中的配置。在应用程序中所做的任何更改都会转到此处(另请参阅下一点)。var|3362596|您还可以使用$APP_HOME/var目录来存储特定于此应用程序实例(而不是用户)的任何其他可变数据。这种方法的另一个优点是，您可以通过简单地复制一个目录来移动和备份整个应用程序及其配置。|3362597|3362598|这说明了一些管理配置的标准技术。您可以使用不同的库和工具来实现它们，从原始JRE开始，添加Spring/Guice，或者使用完整的J2EE容器(可能带有嵌入式Spring)|3362599|管理配置的其他方法包括：|3362600|使用multiple+base+directories运行多个应用程序实例的|3362601|使用不同的configurations.|3362602|Using+lightweight+registries实现集中式配置管理|3362603|一个集中管理的配置管理数据库(CMDB)文件，包含每台计算机的特定于主机的值，每晚都会与所有生产主机进行rsync。应用程序使用模板化配置，并在运行时根据当前主机名从CMDB中进行选择。|3362604|3362605|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#load(java.io.InputStream)|1|http://static.springframework.org/spring/docs/2.5.x/reference/index.html|2|http://xstream.codehaus.org/|3|http://www.xom.nu/|4|http://static.springframework.org/spring/docs/2.5.x/reference/extensible-xml.html|5|http://www.ibm.com/developerworks/library/j-serialtest.html|6|http://java.sun.com/j2se/1.5.0/docs/api/java/util/prefs/Preferences.html|7|http://java.sun.com/j2se/1.4.2/docs/api/java/util/prefs/PreferencesFactory.html|8|http://azeditech.com/tomcat/multiple-tomcat-instances.html|9|http://www.mulesource.org/display/GALAXY/Home|10|http://wso2.org/projects/registry^0|0|0|5|E|0|0|0|J|6|1|2C|7|2|36|3|3|47|N|4|0|0|G|K|5|13|8|6|7A|I|7|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|2|P|8|0|0|6|B|9|I|A|A|0|0|0^^$0|@$1|2|3|4|5|6|7|2J|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|2L|8|@]|9|@$F|2M|G|2N|1|2O]]|A|$]]|$1|H|3|I|5|E|7|2P|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|2Q|8|@]|9|@$F|2R|G|2S|1|2T]|$F|2U|G|2V|1|2W]|$F|2X|G|2Y|1|2Z]|$F|30|G|31|1|32]]|A|$]]|$1|L|3|M|5|E|7|33|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|34|8|@]|9|@$F|35|G|36|1|37]|$F|38|G|39|1|3A]|$F|3B|G|3C|1|3D]]|A|$]]|$1|P|3|-4|5|6|7|3E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|3F|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|3G|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|3H|8|@]|9|@]|A|$]]|$1|V|3|W|5|E|7|3I|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|3J|8|@]|9|@]|A|$]]|$1|Z|3|10|5|E|7|3K|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|3L|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|3M|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|3N|8|@]|9|@]|A|$]]|$1|15|3|16|5|E|7|3O|8|@]|9|@]|A|$]]|$1|17|3|18|5|E|7|3P|8|@]|9|@]|A|$]]|$1|19|3|1A|5|E|7|3Q|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|E|7|3R|8|@]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3V|8|@]|9|@$F|3W|G|3X|1|3Y]]|A|$]]|$1|1K|3|1L|5|E|7|3Z|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|E|7|40|8|@]|9|@$F|41|G|42|1|43]|$F|44|G|45|1|46]]|A|$]]|$1|1O|3|1P|5|E|7|47|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|48|8|@]|9|@]|A|$]]|$1|1R|3|-4|5|6|7|49|8|@]|9|@]|A|$]]]|1S|$1T|$5|1U|1V|1W|A|$1X|1Y]]|1Z|$5|1U|1V|1W|A|$1X|20]]|21|$5|1U|1V|1W|A|$1X|22]]|23|$5|1U|1V|1W|A|$1X|24]]|25|$5|1U|1V|1W|A|$1X|26]]|27|$5|1U|1V|1W|A|$1X|28]]|29|$5|1U|1V|1W|A|$1X|2A]]|2B|$5|1U|1V|1W|A|$1X|2C]]|2D|$5|1U|1V|1W|A|$1X|2E]]|2F|$5|1U|1V|1W|A|$1X|2G]]|2H|$5|1U|1V|1W|A|$1X|2I]]]]

First on the format:

<ol>
<li>Java <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#load(java.io.InputStream)" rel="noreferrer">property files</a> are good for key/value pairs (also automatically handle the newline chars). A degree of structure is possible by using 'dot notation'. Drawback is that the structure does not allow you to easily enumerate top-level configuration entities and work in drill-down manner. Best used for a small set of often tweakable environment-specific settings</li>
<li>XML files - quite often used for more complex configuration of various Java frameworks (notably J2EE and Spring). I would advice that you at least learn about <a href="http://static.springframework.org/spring/docs/2.5.x/reference/index.html" rel="noreferrer">Spring</a> - it contains many ideas worth knowing even if you decide not to use it. If you decide to roll your own XML configuration, I'd recommend using <a href="http://xstream.codehaus.org/" rel="noreferrer">XStream</a> with customized serialization options or if you just need to parse some XML, take a look at <a href="http://www.xom.nu/" rel="noreferrer">XOM</a>. BTW Spring also allows you to plug your custom XML configuration language, but it's a <a href="http://static.springframework.org/spring/docs/2.5.x/reference/extensible-xml.html" rel="noreferrer">relatively complex task</a>. XML configuration is best used for more complex 'internal' configuration that is not seen or tweaked by the end user.</li>
<li>Serialized Java objects - a quick and easy way to persist the state of an object and restore it later. Useful if you write a configuration GUI and you don't care if the configuration is human readable. Beware of <a href="http://www.ibm.com/developerworks/library/j-serialtest.html" rel="noreferrer">compatibility issues</a> when you evolve classes.</li>
<li>Preferences - introduced in <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/prefs/Preferences.html" rel="noreferrer">Java 1.4</a>, allow you to store typed text, numbers, byte arrays and other primitives in platform-specific storage. On Windows, that is the registry (you can choose between /Software/JavaSoft/Prefs under HKLM or HKCU). Under Unix the same API creates files under the user home or /etc. Each prefs hive can be exported and imported as XML file. You can specify custom implementation of the <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/prefs/PreferencesFactory.html" rel="noreferrer">PreferencesFactory</a> interface by setting the "java.util.prefs.PreferencesFactory" JVM property to your implementation class name.</li>
</ol>

In general using the prefs API can be a good or a bad thing based on your app scenario. 

<ol>
<li>If you plan to have multiple versions of the same code running on the same machine with different configuration, then using the Preferences API is a bad idea.</li>
<li>If you plan using the application in a restricted environment (Windows domain or tightly managed Unix box) you need to make sure that you have proper access to the necessary registry keys/directories. This has caught me by surprise more than once.</li>
<li>Beware from roaming profiles (replicated home dirs) they make up for some funny scenarios when more than one active machines are involved.</li>
<li>Preferences are not as obvious as a configuration file under the application's directory. most of the desktop support staff doesn't expect and doesn't like them.</li>
</ol>

Regarding the file layout of the prefs it again depends on your application. A generic suggestion is: 

<ol>
<li>Package most of your XML files inside application's JAR either in the root or under /META-INF directory. These files will be read-only and are considered private for the application.</li>
<li>Put the user modifiable configuration under $APP_HOME/conf . It should consist mainly of properties files and occasionally a simple XML file (XStream serialization). These files are tweaked as part of the installation process and are usually not user serviceable.</li>
<li>Under the user-home, in a dot-directory (i.e. '~/.myapplication') store any user configuration. The user configuration may override the one in the application conf directory. Any changes made from within the application go here (see also next point). </li>
<li>You can also use an $APP_HOME/var directory to store any other mutable data which is specific to this application instance (as opposed to the user). Another advantage of this approach is that you can move and backup the whole application and it's configuration by simple copy of one directory.</li>
</ol>

This illustrates some standard techniques for managing configuration. You can implement them using different libraries and tools, starting from raw JRE, adding Spring/Guice or going for a full J2EE container (possibly with embedded Spring)

Other approaches for managing configuration are:

<ol>
<li>Using <a href="http://azeditech.com/tomcat/multiple-tomcat-instances.html" rel="noreferrer">multiple base directories</a> for running multiple instances of the application using different configurations.</li>
<li>Using <a href="http://www.mulesource.org/display/GALAXY/Home" rel="noreferrer">lightweight</a> <a href="http://wso2.org/projects/registry" rel="noreferrer">registries</a> for centralized configuration management</li>
<li>A centrally managed Configuration Management Database (CMDB) file, containing the host-specific values for each machine is rsync-ed every night to all production hosts. The application uses a templated configuration and selects from the CMDB during runtime based on the current hostname.</li>
</ol>

Where do you store user-specific and machine-specific runtime configuration data for J2SE application?
(For example, C:\Users\USERNAME\AppData\Roaming&lt;/em&gt; on Windows and /home/username on Unix)
How do you get these locations in the filesystem in platform-independent way?

What is the proper way to store app's conf data in Java?

文件系统

数据库

Windows

Eclipse

容器

Java

Unix

您在哪里存储特定于用户和特定于计算机的J2SE应用程序的运行时配置数据？(例如，Windows上的C：\Users\用户名\AppData\Roaming和Unix上的/home/username )如何以独立于平台的方式在文件系统中获取这些位置？

问在Java中存储app的conf数据的正确方式是什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Java中存储app的conf数据的正确方式是什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Java中存储app的conf数据的正确方式是什么？
EN