Problem | An error occurred while generating default bindings for all EJBs contained in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | An error occurred while generating bindings for all EJB references in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | An error occurred while generating bindings for all resource references in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | An error occurred while generating bindings for all resource-env reference in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | An error occurred while generating virtual host bindings for all web modules in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | An EJB with the same name already exists in the application. |
User response | none if the same name is used in an EJB belonging to different ejb jar file. If same name is used in the same ejb jar file, then validate your application using Application Assembly Tool. |
Problem | An EJB with the name as specified in the ejb-link does not exist in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | An EJB with the home interface as specified by the EJB reference does not exist in the application. |
User response | Validate your application using Application Assembly Tool. |
Problem | There is more than one matching EJB with the same home interface as specified by the EJB reference |
User response | Add ejb link element including the path name of the ejb jar that contains the reference enterprise bean. Validate your application using Application Assembly Tool. |
Problem | There is no connection factory binding for both the specified CMP bean and in the JAR which it belongs. |
User response | Rerun default bindings by providing the JNDI name for default connection factory or specify the connection factory binding during application install. |
Problem | There is no data source binding for both the specified CMP bean and in the JAR which it belongs. |
User response | Rerun default bindings by providing the JNDI name for a default data source or specify the data source binding during applicaiton install. |