blocks|key|2072232|text|我不会将其存储在应用程序文件夹中，因为这会用应用程序的新部署覆盖配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2072233|我建议您查看一下Preferences+API，或者在users文件夹(运行Tomcat的用户)中编写一些内容。|2072234|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would not store it in the application folder, because that would override the configuration with a new deployment of the application.

I suggest you have a look at the Preferences API, or write something in the users folder (the user that is running Tomcat).

blocks|key|1858458|text|这个问题的答案取决于您打算如何读取和写入配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1858459|例如，Spring框架提供了use+XML+configuration+files+(或Java属性文件)的能力；这些文件可以存储在您的类路径中(例如，在WEB-INF目录中)、文件系统上的任何其他地方，甚至是内存中。如果您要使用Spring来实现这一点，那么存储配置文件的最简单位置就是WEB-INF目录，然后使用Spring的ClassPathXmlApplicationContext类来访问您的配置文件。|offset|length|1858460|但是，这完全取决于您计划如何访问该文件。|1858461|entityMap|0|LINK|mutability|MUTABLE|url|http://static.springframework.org/spring/docs/2.5.x/reference/beans.html#beans-factory-instantiation|1|http://static.springframework.org/spring/docs/2.0.x/api/org/springframework/context/support/ClassPathXmlApplicationContext.html^0|0|E|R|0|4L|U|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]|$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

The answer to this depends on how you intend to read and write that config file.

For example, the Spring framework gives you the ability to <a href="http://static.springframework.org/spring/docs/2.5.x/reference/beans.html#beans-factory-instantiation" rel="nofollow noreferrer">use XML configuration files</a> (or Java property files); these can be stored in your classpath (e.g., in the WEB-INF directory), anywhere else on the filesystem, or even in memory. If you were to use Spring for this, then the easiest place to store the config file is in your WEB-INF directory, and then use Spring's <a href="http://static.springframework.org/spring/docs/2.0.x/api/org/springframework/context/support/ClassPathXmlApplicationContext.html" rel="nofollow noreferrer">ClassPathXmlApplicationContext</a> class to access your configuration file.

But again, it all depends on how you plan to access that file.

blocks|key|1858645|text|如果它是您的自定义配置，则WEB-INF是一个很好的位置。但是一些库可能需要配置驻留在WEB-INF/classes中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1858646|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|$]]

If it is your custom config WEB-INF is a good place for it. But some libraries may require configs to reside in WEB-INF/classes.

blocks|key|2072669|text|我们要做的就是把它放在服务器上的一个单独的目录中(你可以使用类似/config，/opt/config，/root/config，/home/username/config，或者你想要的任何东西)。当我们的servlet启动时，它们读取XML文件，从中获取一些东西(最重要的是数据库连接信息)，仅此而已。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2072670|我问过我们为什么要这样做一次。|2072671|将所有内容都存储在数据库中是很好的，但显然您不能将数据库连接信息存储在数据库中。|2072672|你可以在代码中硬编码一些东西，但是由于许多原因，这是丑陋的。如果信息发生变化，您必须重新构建代码并重新部署。如果有人获得了您的代码或WAR文件的副本，那么他们就会获得这些信息。|2072673|将内容放在WAR文件中似乎很好，但如果您想更改很多内容，这可能是一个糟糕的主意。问题是，如果您必须更改信息，那么下次重新部署时，它将覆盖该文件，因此您在构建到WAR中的版本中忘记更改的任何内容都会被遗忘。|2072674|文件系统中特殊位置的文件对我们来说工作得很好。它没有任何大的缺点。您知道它在哪里，它是单独存储的，如果它们都需要不同的配置值(因为它不是WAR的一部分)，那么部署到多台机器上就很容易。|2072675|我能想到的唯一有效的其他解决方案是将除了数据库登录信息之外的所有内容都保存在数据库中。这将来自通过JVM检索的Java系统属性。这就是Hans+Doggen上面提到的Preferences+API。我不认为它是在我们的应用程序第一次开发的时候出现的，如果它是没有被使用的话。|2072676|至于访问配置文件的路径，它只是文件系统上的一个文件。你不需要担心web路径。因此，当您的servlet启动时，它只需打开"/config/myapp/config.xml“(或其他文件)中的文件，它就会找到正确的内容。对我来说，硬编码这条路径似乎没有什么坏处。|2072677|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

What we do is to put it in a separate directory on the server (you could use something like /config, /opt/config, /root/config, /home/username/config, or anything you want). When our servlets start up, they read the XML file, get a few things out of it (most importantly DB connection information), and that's it.

I asked about why we did this once.

It would be nice to store everything in the DB, but obviously you can't store DB connection information in the DB.

You could hardcode things in the code, but that's ugly for many reasons. If the info ever has to change you have to rebuild the code and redeploy. If someone gets a copy of your code or your WAR file they would then get that information.

Putting things in the WAR file seems nice, but if you want to change things much it could be a bad idea. The problem is that if you have to change the information, then next time you redeploy it will overwrite the file so anything you didn't remember to change in the version getting built into the WAR gets forgotten.

The file in a special place on the file system thing works quite well for us. It doesn't have any big downsides. You know where it is, it's stored seperatly, makes deploying to multiple machines easy if they all need different config values (since it's not part of the WAR).

The only other solution I can think of that would work well would be keeping everything in the DB except the DB login info. That would come from Java system properties that are retrieved through the JVM. This the Preferences API thing mentioned by Hans Doggen above. I don't think it was around when our application was first developed, if it was it wasn't used.

As for the path for accessing the configuration file, it's just a file on the filesystem. You don't need to worry about the web path. So when your servlet starts up it just opens the file at "/config/myapp/config.xml" (or whatever) and it will find the right thing. Just hardcodeing the path in for this one seems pretty harmless to me.

blocks|key|2072780|text|WEB-INF是放置配置文件的好地方。下面是从servlet获取目录绝对路径的一些代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2072781|public+void+init(ServletConfig+servletConfig)+throws+ServletException{
++++super.init(servletConfig);
++++String+path+=+servletConfig.getServletContext().getRealPath("/WEB-INF")|code-block|syntax|javascript|2072782|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

WEB-INF is a good place to put your config file. Here's some code to get the absolute path of the directory from a servlet.

<pre><code>public void init(ServletConfig servletConfig) throws ServletException{
 super.init(servletConfig);
 String path = servletConfig.getServletContext().getRealPath("/WEB-INF")
</code></pre>

blocks|key|1859060|text|将其放入WEB-INF将对试图通过URL直接访问它的用户隐藏该文件，因此，是的，我建议将其放入WEB-INF。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1859061|entityMap^0|4|7|1B|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Putting it in <code>WEB-INF</code> will hide the XML file from users who try to access it directly through a URL, so yes, I'd say put it in <code>WEB-INF</code>.

I create a web application (WAR) and deploy it on Tomcat. In the webapp there is a page with a form where an administrator can enter some configuration data. I don't want to store this data in an DBMS, but just in an XML file on the file system. Where to put it?

I would like to put the file somewhere in the directory tree where the application itself is deployed. Should my configuration file be in the WEB-INF directory? Or put it somewhere else? 

And what is the Java code to use in a servlet to find the absolute path of the directory? Or can it be accessed with a relative path?

What is the best place to store a configuration file in a Java web application (WAR)?

我创建了一个web应用程序(WAR)并将其部署在Tomcat上。在webapp中有一个带有表单的页面，管理员可以在其中输入一些配置数据。我不想将这些数据存储在DBMS中，而只是存储在文件系统上的一个XML文件中。把它放在哪里？我希望将该文件放在部署应用程序本身的目录树中的某个位置。我的配置文件应该在WEB-INF目录中...

问在Java web应用程序(WAR)中存储配置文件的最佳位置是什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Java web应用程序(WAR)中存储配置文件的最佳位置是什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Java web应用程序(WAR)中存储配置文件的最佳位置是什么？
EN