The problem was that the WAS version does not have availability for servlets 3.0
First you have to see what the complete error is, so I consulted the SystemErr.log file of the Websphere which is in
Root Installation\IBM\WebSphere\${TuServidor}\profiles\${TuServidor}\logs\server1.
The complete error of this case was: '
[26/09/17 12:23:07:784 CDT] 0000002f SystemErr R AppDeploymentException: [null]
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: dd_in_ear_load_EXC_
[26/09/17 12:23:07:784 CDT] 0000002f SystemErr R org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: dd_in_ear_load_EXC_
Stack trace of nested exception:
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: WEB-INF/web.xml
Stack trace of nested exception:
java.lang.IllegalStateException: Parent Translator (GenericTranslator(servlet,1026440494)) did not find a Child Translator for "multipart-config".
By digging a bit I find that "multipart-config" refers to a version error with servlets. I used Servlets 3.0 in my application and tried to install it in a WAS6.1. The IBM page provides us with the following information:
Which tells us that to use servlets 3.0 we need minimum version 8.0 of the Websphere
Unfortunately in my case there was nothing left but to downgrade my code and adapt to the specifications that are there to develop for websphere 6.1