WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS


BNDE

BNDE0000E: Could not bind EJBs: {0}
Explanation An error occurred generating the default bindings for all of the enterprise Java beans (EJBs) that are contained in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0001E: Could not bind EJB references: {0}
Explanation An error occurred generating the bindings for all of the references for the enterprise Java beans (EJBs) in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0002E: Could not bind resource references: {0}
Explanation An error occurred generating the bindings for all of the resource references in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0003E: Could not bind resource-env references: {0}
Explanation An error occurred while generating the bindings for all of the resource-env references in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0004E: Could not bind virtual host(s): {0}
Explanation An error occurred generating the bindings for the virtual host for all the web modules in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0005W: Duplicate <ejb-name> encountered: {0}
Explanation An enterprise Java bean (EJB) with the same name already exists in the application.
Action 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.
BNDE0006W: <ejb-link> could not be resolved: {0}
Explanation An enterprise Java bean (EJB) with the name that is specified in the EJB link element does not exist in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0007W: EJB reference could not be resolved: {0}
Explanation An enterprise Java bean (EJB) with the home interface that is specified by the EJB reference does not exist in the application.
Action Validate your application using the Application Assembly Tool.
BNDE0008W: ambiguous EJB reference to {0} - use <ejb-link> to clarify
Explanation There is more than one matching enterprise Java bean (EJB) with the same home interface that is specified by the EJB reference.
Action 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.
BNDE0009W: CMP Bean {0} does not have a connection factory binding
Explanation 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.
Action 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.
BNDE0010W: CMP Bean {0} does not have a data source binding
Explanation 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.
Action 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.
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:56:37 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.BindEarCmd.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)