title: How to correctly refactor ibm-ejb-jar-bnd.xmi file while doing app migration from WebSphere Application Server traditional to Liberty?
body: <p>I am facing an error while doing app migration from WebSphere Application Server traditional v9.0.0.7 to Liberty base v18.0.0.1</p>
  
  <p>An exceptions in console says:</p>
  
  <pre><code>...
      CWWKZ0002E: An exception occurred while starting the application AP. The exception message was: com.ibm.ws.container.service.metadata.MetaDataException: com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ejs.container.EJBConfigurationException: com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: 
      CWWKC2251E: The ejbBindings element is missing the required name attribute in the /META-INF/ibm-ejb-jar-bnd.xmi deployment descriptor on line 9.
  ...
  </code></pre>
  
  <p>It seems like there is an issue with EJB binding.
  I have been reading that Liberty doesn't support WAS 9 EJBs binding and only binds EJBs to the <strong>java : namespace</strong> syntax.</p>
  
  <p><strong>ibm-ejb-jar-bnd.xmi</strong> file looks like:</p>
  
  <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:ejb="ejb.xmi" xmlns:ejbbnd="ejbbnd.xmi" xmi:id="EJBJarBinding_1090575365340"&gt;
    &lt;ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/&gt;
    &lt;ejbBindings xmi:id="EnterpriseBeanBinding_1090575365340" jndiName="ejb/com/ap/ejb/AccountSessionHome"&gt;
      &lt;enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AccountSession"/&gt;
    &lt;/ejbBindings&gt;
    &lt;ejbBindings xmi:id="EnterpriseBeanBinding_1047783791228" jndiName="ejb/com/ap/ejb/UtilitySessionHome"&gt;
      &lt;enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#UtilitySession"/&gt;
    &lt;/ejbBindings&gt;
  &lt;/ejbbnd:EJBJarBinding&gt;
  </code></pre>
  
  <p>How exactly should I refactor the ibm-ejb-jar-bnd.xmi file? 
  Please help me to sort out the issue.</p>