The "ear file may be corrupted and incomplete" solution was encountered when deploying an application (such as war) under was (WebSphere6 or WebSphere7)

The ear file may be corrupted and/or incomplete. Ensure that the application is in the current version of WebSphere (R) Application Server compatible Java (TM) Platform, Enterprise Edition (Java EE) level.

Analysis:

Knowing that the problem is caused by using the <tablib> tag under the Web-app node in the Web. xml file by viewing the log is that when the Web-app version of the Web. xml file is 2.4, the <tablib> tag needs to be nested on the outer layer <jsp-config> tags.

Note: Because WebSphere has strict requirements on the Web. xml file configuration specification, reference <tablib> Improper is just one of the reasons for the above problem. Other reasons such as the incorrect order of filter and servlet configuration in the Web. xml file can also cause the above problem.

Modify the following:

<web-app>

...

...

<jsp-config>

<taglib>
<taglib-uri>xxx</taglib-uri>
<taglib-location>xxxxxx</taglib-location>
</taglib>
</jsp-config>
</web-app>