
2019阿里云全部产品优惠券(新购或更新都可以使用,强烈推荐)
领取地址:
I'm getting the following error when trying to deploy an ear with websphere from an ant ask with jacl:
[wsadmin] WASX7017E: Exception received while running file "C:\...\AppData\Local\Temp\wsant6857788060872488512jacl"; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: WEB-INF/web.xml]
When I try to deploy the ear from the websphere console I get:
The following exception occurred. Check log for details.
com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: WEB-INF/web.xml]

Machine details: Win7x64, WebSphere 8.5 x86, using oracle jdk 6u30 x86 (Tested with x64 too).
Others have been able to get the installer to work for them. The WebSphere connection information is correct, as other scripts properly update
d libraries. I'm baffled why it works on other machines and not this one... any answers/suggestions are appreciated.
|
this question asked Dec 18 '12 at 18:51 James Oravec 6,604 10 46 89 1 You got a hint there "Check log for details", give us the details – Aviram Segal Dec 18 '12 at 20:43 1 The exception is referring you to the web.xml of an application in your EAR. Do all the WARs in your EAR have a web.xml file? Can you see if there is an error with any of the web.xml files? – Nick Roth Dec 18 '12 at 20:48 |解决方法
After much searching (even posted a bounty on a similar problem), I found the issue was comments in the web.xml.
![]()
I was lucky enough to have a source branch that didn't have the comments and worked and this other branch that did have the comments and was broke. Different installers from different branches is what allowed the installers to work on some machines, and this other branch installer breaking on my machine.
Removing the comments allowed WebSphere's validator to get past that error... fun stuff... will report it to the WebSphere guys.
|
this answer answered Dec 18 '12 at 23:28 James Oravec 6,604 10 46 89 1 Looks like WebSphere already knows about it, and they have patches available... <sigh> www-01.ibm.com/support/docview.wss?uid=swg1PM49316 – James Oravec Dec 18 '12 at 23:37 I had similar problem. I didn't have any comments in web.xml. Solution for me was to close project and open it again. I don't understand how it helped... – jasiustasiu Nov 13 '14 at 11:25 |
Same error occurred for me, but problem was in the application.xml not the web.xml, spec was inconsistent between application.xml and web.xml. Web 3.0, J2EE 1.4, should have been Java EE 6.
|

this answer 30.5k 7 77 118 answered Jan 14 '15 at 14:08 Jason Crow 21 2 |
Please check the application.xml file in ear which has the correct war file name and also check the ejb module jar names. you will get similar error if there is a mismatch in war or ejb jar file names. My case I have issue in the war file name that was wrongly specified in the application.xml
|
this answer answered Sep 9 '15 at 17:30 Palanivel 21 1 Up voted. My war file name was misspelled in the application.xml – minil Nov 3 '16 at 15:49 |
In my case.
I did these steps:-

Go to the EAR
2.Right Click -> Select Properties.
3.Click on Deployment Assembly
4.Add/Remove -WebApps to the EAR.
5.Click on the un-identified project. First Remove it and Added it Again.
|
this answer answered Jan 27 '15 at 18:15 Sireesh Yarlagadda 4,198 1 31 41 |
本文来自电脑杂谈,转载请注明本文网址:
https://www.pc-fly.com/a/jisuanjixue/article-127154-1.html
豈不皆大歡喜
那个女的是