BNDEAR0010=BNDE0010W: CMP Bean {0} does not have a data source binding There is no Datasource binding for both the container-managed persistence (CMP) bean that is specified and in the JAR file to which it belongs. Rerun default bindings by providing the Java Naming and Directory Interface (JNDI) name for a default Datasource or specify the Datasource binding during application installation. BNDEAR0009=BNDE0009W: CMP Bean {0} does not have a connection factory binding There is no connection factory binding for both the container-managed persistence (CMP) bean that is specified and in the JAR file to which it belongs. Rerun the default bindings by providing the Java Naming and Directory Interface (JNDI) name for the default connection factory or specify the connection factory binding when you install the application. BNDEAR0008=BNDE0008W: ambiguous EJB reference to {0} - use <ejb-link> to clarify There is more than one matching enterprise Java bean (EJB) with the same home interface that is specified by the EJB reference. Add the EJB link element that includes the path name of the JAR file for the EJB that contains the enterprise bean that is being referenced. Validate your application using the Application Assembly Tool. BNDEAR0007=BNDE0007W: EJB reference could not be resolved: {0} An enterprise Java bean (EJB) with the home interface that is specified by the EJB reference does not exist in the application. Validate your application using the Application Assembly Tool. BNDEAR0006=BNDE0006W: <ejb-link> could not be resolved: {0} An enterprise Java bean (EJB) with the name that is specified in the EJB link element does not exist in the application. Validate your application using the Application Assembly Tool. BNDEAR0005=BNDE0005W: Duplicate <ejb-name> encountered: {0} An enterprise Java bean (EJB) with the same name already exists in the application. There is no user action required if the same name is used in an EJB that belongs to a different JAR file for the EJB. If same name is used in the same JAR file for the EJB, then validate your application using the Application Assembly Tool. BNDEAR0004=BNDE0004E: Could not bind virtual host(s): {0} An error occurred generating the bindings for the virtual host for all the web modules in the application. Validate your application using the Application Assembly Tool. BNDEAR0003=BNDE0003E: Could not bind resource-env references: {0} An error occurred while generating the bindings for all of the resource-env references in the application. Validate your application using the Application Assembly Tool. BNDEAR0002=BNDE0002E: Could not bind resource references: {0} An error occurred generating the bindings for all of the resource references in the application. Validate your application using the Application Assembly Tool. BNDEAR0001=BNDE0001E: Could not bind EJB references: {0} An error occurred generating the bindings for all of the references for the enterprise Java beans (EJBs) in the application. Validate your application using the Application Assembly Tool. BNDEAR0000=BNDE0000E: Could not bind EJBs: {0} An error occurred generating the default bindings for all of the enterprise Java beans (EJBs) that are contained in the application. Validate your application using the Application Assembly Tool.