Explanation | An error occurred performing the binding validation for the enterprise Java bean (EJB). This is an internal implementation error. Partial validation has been performed. |
Action | Visit the product support web site for information on problem determination. |
Explanation | There is JAR reference value for the enterprise Java bean (EJB) that is null and not valid in the JAR binding for the EJB. |
Action | Update the binding information for the EJB to correct the specified problem. |
Explanation | An enterprise Java bean (EJB) reference to an EJB binding is null or not valid. |
Action | Update the EJB binding information to correct the specified problem. |
Explanation | No binding information has been specified for the enterprise Java bean (EJB). Binding information such as Java Naming and Directory Interface (JNDI) names must be specified for all the beans in an JAR file for the EJB before the module can be started in the Application Server. |
Action | Update the information for the EJB binding to correct the specified problem. |
Explanation | No binding information has been specified for the enterprise Java bean (EJB). Binding information such as Java Naming and Directory Interface (JNDI) names must be specified for all the beans in an JAR file for the EJB before the module can be started in the Application Server. |
Action | Update the information for the EJB binding to correct the specified problem. |
Explanation | An enterprise Java bean (EJB) binding with a EJB reference that is null or not valid has been detected in the EJB bindings. |
Action | Update the EJB binding information to correct the specified problem. |
Explanation | No Java Naming and Directory Interface (JNDI) name has been specified for the enterprise Java bean (EJB) reference for the home. JNDI names must be specified for all the EJB references in the JAR file for the EJB before the module can be started in the application server. |
Action | Update the EJB binding information to correct the specified problem. |
Explanation | An enterprise Java bean (EJB) binding with a resource reference that is null or not valid has been detected in the EJB bindings under EJB {0}. |
Action | Update the information for the EJB binding to correct the specified problem. |
Explanation | No Java Naming and Directory Interface (JNDI) name has been specified for the resource reference. JNDI names must be specified for all the resource references in the JAR file for the EJB before the module can be started in the Application Server. |
Action | Update the information for the EJB binding to correct the specified problem. |
Explanation | No data source has been specified for the container-managed entity bean. The default data source that is specified in the JAR file for the enterprise Java bean (EJB) will be used. |
Action | Update the information for the EJB binding to correct the specified problem. |
Explanation | No JNDI name for a data source has been specified for the container managed entity bean. The default data source that is specified in the JAR file enterprise Java bean (EJB) will be used. |
Action | Update the information for the EJB binding to correct the specified problem. |
Explanation | No default container-managed persistence (CMP) data source has been specified for this JAR file for the enterprise Java bean (EJB), and some container managed entity beans do not have CMP data source JNDI names specified. The default CMP data source of the EJB Container will be used for all the container-managed entity beans with no CMP data source that is specified. |
Action | Update the information for the EJB binding to correct the specified problem. |