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


CHKW enterprise bean binding validation

CHKW4500E: An internal error has occurred. Please check the log files for more information on the error occurred.
Explanation An error occurred while performing EJB binding validation. This is an internal implementation error. Partial validation has been performed.
Action Contact support for further assistance.
CHKW4510E: Invalid null EJB jar reference in EJB jar binding.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4511E: An EJB binding with an invalid or null EJB reference has been detected in the EJB bindings.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4512W: No binding information has been specified for EJB, {0}. Binding information such as JNDI names must be specified for all EJB in an EJB jar before the module may be started in the application server.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4513W: No JNDI name has been specified for EJB, {0}. JNDI names must be specified for all EJB in an EJB jar before they can be started in the application server.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4514E: An EJB binding with an invalid or null EJB reference has been detected in the EJB bindings under EJB {0}.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4515W: No JNDI name has been specified for the EJB ref for home {0} under EJB {1}. JNDI names must be specified for all EJB refs in the EJB jar before the module may be started in the application server.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4516E: An EJB binding with an invalid or null resource reference has been detected in the EJB bindings under EJB {0}.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4517W: No JNDI name has been specified for the resource ref for resource of name {0} and type {1} under ejb {2}. JNDI names must be specified for all resource refs in the ejb jar before the module may be started in the application server.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4518W: No datasource has been specified for the container managed entity bean {0}. The default datasource specified for the EJB jar will be used.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4519W: No JNDI name for a datasource has been specified for the container managed entity bean {0}. The default datasource specified for the ejb jar will be used.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
CHKW4520W: No default CMP datasource has been specified for this ejb jar, and some container managed entity beans do not have CMP datasource JNDI names specified. The default CMP datasource of the EJB Container will be used for all container managed entity beans with no CMP datasource specified.
Explanation None is available.
Action Update the EJB binding information to correct the specified problem.
Reference topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 6:45:20 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.websphere.validation.base.bindings.ejbbnd.ejbbndvalidation.html

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