部署到 OC4j:无法找到/读取文件 META-INF/application.xml
Continuum 构建服务器部署到我的 oc4j 实例时,我收到以下错误,似乎每个其他构建都出现此错误。
2010 年 9 月 3 日 13:47:49 通知 ==> 操作失败并出现错误: 无法在 C:\oc4j\j2ee\home\applications\rrs (META-INF/application.xml) 中找到/读取文件 META-INF/application.xml
Continuum 正在 Windows 环境中运行
任何输入将不胜感激。
Continuum build server deploys to my oc4j instance I get the following error it seems every other build.
09/03/10 13:47:49 Notification ==>Operation failed with error:
Unable to find/read file META-INF/application.xml in C:\oc4j\j2ee\home\applications\rrs (META-INF/application.xml)
Continuum is running in a windows environment
Any input would be greatly appreciated.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我不使用 Continuum,但在某些应用程序部署期间遇到此 OC4J 消息。
该错误消息表明您正在部署的 EAR 中缺少 application.xml 文件。 您正在主实例中部署一个名为 rss 的应用程序。 rss.ear 文件内必须存在 META-INF/application.xml,其内容如下:
在构建过程的某个步骤中,您必须定义并包含 application.xml 文件。 也许您正在使用的工具可以做到这一点,但需要一些配置。
I don't use Continuum, but I face this OC4J message during some app deployments.
The error message shows that the application.xml file is missing inside the EAR you are deploying. You are deploying an application called rss in the home instance. Inside the rss.ear file must be present a META-INF/application.xml with a content like this:
In some step of your building process you must define and include the application.xml file. Perhaps the tool you are using could do this, but need some configuration.
我听说有时这是一个 Windows 问题。 我还注意到,在 eclipse 中使用 oc4j 服务器适配器,当我的发布命令由于任何错误而无法部署我的战争时,我会看到这种行为。 然后,下次我尝试发布/部署时,会显示“无法查找/读取文件 META-INF/application.xml”错误,并且部署失败,必须重复一次。 就好像失败的部署在错误的地方留下了一些残留物。 不是解决方案,只是一些观察...
I have heard this is a windows issue sometimes. I have also noticed that in eclipse using the oc4j server adapter I see this behavior when my publish command fails to deploy my war due to any error at all. Then the next time I try to publish/deploy The error for "Unable to find/read file META-INF/application.xml" is displayed and the deploy fails and must be repeated once. It is as if the failed deploy left some remnants in the wrong place. not a solution just some observations...