[转]java.util.MissingResourceException: Can't find bundle for base name

最新推荐文章于 2023-09-23 12:54:13 发布

weixin_30436101

最新推荐文章于 2023-09-23 12:54:13 发布

阅读量128

点赞数

CC 4.0 BY-SA版权

文章标签： runtime java

原文链接：http://www.cnblogs.com/avenxia/archive/2011/12/16/2290061.html

本文介绍了如何解决Java中资源文件加载导致的MissingResourceException异常。通过调整资源文件的位置和引用方式，确保类加载器能够正确加载指定的资源。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

java.util.MissingResourceException: Can't find bundle for base name

2008-09-24 15:47

java.util.MissingResourceException: Can't find bundle for base name

2007-08-13 21:59

头午写那个程序，人家老大说了，得要配活。。。怎么配活呢。读取一个文本文件，这样就活啦。晕。。。

下午就开始了。。。文件属性及值都搞好了，然而在配属性文件时出现标题的样子错误。然后在网上找呀找。。终于找到了，NND，可惜是英文的，不过俺的英语还能看个八九不离十。。

Solve java.util.MissingResourceException: Can't find bundle for base name com...config, locale zh_CN

at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:836)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:805)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:576)

You know java is looking for a properties file in a specific locale. You may be baffled why java keeps complaining it can't find a properties file that is right there. A few things to keep in mind when debugging this type of errors:

These resource properties files are loaded by classloader, similar to java classes. So you need to include them in your runtime classpath.
These resources have fully-qualified-resource-name, similar to a fully-qualified-class-name, excerpt you can't import a resource into your java source file. Why? because its name takes the form of a string.
ResourceBundle.getBundle("config") tells the classloader to load a resource named "config" with default package (that is, no package). It does NOT mean a resource in the current package that has the referencing class.
ResourceBundle.getBundle("com.cheng.scrap.config") tells the classloader to load a resource named "config" with package "com.cheng.scrap." Its fully-qualified-resource-name is "com.cheng.scrap.config"

For instance, you have a project like

For this statement in Scrap.java: ResourceBundle config = ResourceBundle.getBundle("config"); to work, you will need to cp src\com\cheng\scrap\config.properties build\classes\ such that config.properties is directly under classes, and at the same level as com. Alternatively, you can put config.properties into a config.jar such that config.properties is at the root of config.jar without any subdirectories, and include config.jar in the classpath.

For this statement in Scrap.java: ResourceBundle config = ResourceBundle.getBundle("com.cheng.scrap.config"); to work, you will need to cp src\com\cheng\scrap\config.properties build\classes\com\cheng\scrap\ such that config.properties is directly under classes\com\cheng\scrap\, and at the same level as scrap. Alternatively, you can put com\cheng\scrap\config.properties (along with the long subdirectories) into a config.jar, and include config.jar in the classpath.

You may be wondering why it is made so confusing? The benefits are two-fold, as I see it:

Location transparency. At runtime, config.properties is NOT a file, it's just a a loadable resource. config.properites may not exist in your project at all, and the person who wrote Scrap.java may have never seen this resource. A URLClassLoader can find it in a network path or URL at runtime. This is especially important for server-side components such as EJB, Servlet, JSP, etc, who are normally not allowed to access file systems. When you ask classloaders for a resource, its physical location becomes irrelevant.
Namespace mechanism. Having a package allows multiple packages to have resources with the same short name without causing conflicts. This is no different from java packages and xml namespaces.

才知道那个属性文件也要加上路径的。于是又开始新征程。这样为了配活，再来。

static ResourceBundle rb = ResourceBundle.getBundle(ReadSource.class.getPackage().toString().substring(8)+".info");

这样就解决了路径问题，只要属性文件和读取文件在一起就可以了。它们俩放哪倒是无所谓了。呵呵。