A file does not exist for module element having uri

当启动WebSphere的时候报了以下错误：
[color=red]com.ibm.etools.j2ee.commonarchivecore.exception.NoModuleFileException: A file does not exist for module element having uri: XXX.war
at com.ibm.etools.j2ee.commonarchivecore.impl.ModuleRefImpl.checkType(ModuleRefImpl.java:492)
at com.ibm.etools.j2ee.commonarchivecore.impl.ModuleRefImpl.initModuleFileFromEAR(ModuleRefImpl.java:120)
.....................................[/color]

我使用的was6.1，在网上搜索了以下，在IBM的论坛中找到了以下回复
[color=indigo]This can happen if you start changing your build path.

1. Using RAD, take a look at your build path. Right click on the project -> Build Path -> Configure Build Path
2. Click on the Source tab. Take note of what is listed.
3. Open up the file org.eclipse.wst.common.component
4. Is there something listed in the component file that is not listed in the build path? Specifically, something you thought you had gotten rid of, or perhaps something that has a build error in it?

I was trying to debug a problem by manipulating the build path to not include the areas that didn't compile. It pulled them from the build path file, but not this second file. My Java directory showed no errors (because it wasn't in the build path), and my Enterprise Application showed no errors (because it took stuff from the Java project). But, when it tried to start, that's when it found the error, and BURIED it underneath not finding a WAR file -- which it couldn't find, because there were buried errors.

Note: The project having an error is key on this. If there's no error, or if the directory is completely empty, or even missing, it would probably still come up with no problems. And then, many days from now, you add something to that folder which you forgot all about.....and you get this.[/color]

http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14448317