title: Why WAS is looking for ejb jar xml for an EJB 3 application
body: <p>When I try to deploy my EJb 3.0 EAR on WAS 6.1,  iget : </p>
  
  <pre><code>The EAR file could be corrupt and/or incomplete. Make sure that the application is at a compatible Java 2 Platform, Enterprise Edition (J2EE) Level for WebSphere Application Server.
  AppDeploymentException: [META-INF/ejb-jar.xml] org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: META-INF/ejb-jar.xml 
  </code></pre>
  
  <p>But this is an EJB 3.0 application, so why does it look for ejb-jar.xml?</p>