WebSphere Process Server messages     Operating Systems: All supported

CWNEN

CWNEN0001E: The injection engine caught {0} and has created the following error: {1}.
Problem
User response
CWNEN0005E: The injection engine service is not available.
Problem The injection engine service for the specified server is not available.
User response The injection engine service is started as a singleton service on all application server processes. Check that the application server started withut any errors.
CWNEN0006E: The injection engine cannot register the injection processors until the injection engine service is initialized.
Problem The injection engine initializes a set of default injection processors during startup. The injection engine service must be started and initialized before additional injection processors can be registed with the injection engine.
User response Ensure that the injection processors are being registered after the application server is started.
CWNEN0008E: The {0} method must be a setter method; the annotation is ignored.
Problem The method for the injection target must be a setter property method.
User response Ensure that the annotation or injection target XML is specifying the intended method.
CWNEN0009E: The injection engine failed to process the XML code from the deployment descriptor.
Problem There was an error when processing the meta data in the deployment descriptor.
User response Ensure that the XML contained in deployment descriptor is correct.
CWNEN0010E: The injection engine failed to process the {0} or {1} annotation in the {3} class.
Problem The injection engine was unable to properly set up the injection targets for the specified class.
User response Ensure that the correct annotations are contained within the class and within the XML in the deployment descriptor.
CWNEN0011E: The injection engine failed to process bindings for the metadata.
Problem The bindings and injection information contain errors.
User response Ensure that the annotations contained in the class and XML contained in deployment descriptor is correct.
CWNEN0013W: The following NumberFormatException exception occurred when the injection engine attempted to convert the {0} <env-entry-name> {1} <env-entry-value>: {2}
Problem The container cannot process an environment entry due to a NumberFormatException exception.
User response Ensure that the value for the environment entry is a valid string representation for the specified type.
CWNEN0014W: The java:comp/env context environment entry for {0} enterprise bean, which is the Boolean type, is not set to a valid Boolean value: {1}. Thus, the entry is assigned a false value.
Problem A java:comp/env context environment entry for an enterprise bean of the Boolean type should be assigned either a true or false value. Any other value results in false value, but it might indicate a configuration problem. The application might not behave as expected.
User response Change the java:comp/env context environment entry of the Boolean type to either a true or false value.
CWNEN0015W: The following exception has been caught in attempting to construct the {0} <env-entry-name> {1} <env-entry-value>: {2}
Problem The injection engine encountered an exception when it attempted to create a java:comp/env entry.
User response Take action based upon message associated with exception.
CWNEN0016W: A type, which is not valid, has been specified in the following java:comp/env context environment entry for a bean: {0} <env-entry-name>.
Problem The injection engine encountered a type that is not valid for an environment entry.
User response Ensure that you use one of following environment entry types: String, Integer, Boolean, Double, Byte, Short, Long, or Float.
CWNEN0017E: The injection engine cannot resolve the target of the {0} resource-ref declaration to the associated binding location in the global namespace.
Problem The injection engine cannot link between the name that is declared in the java:comp/env namespace and the name of the target resource in the global Java Naming and Directory Interface (JNDI) namespace.
User response Ensure that the name that is declared on the injection, using @Resource annotation or resource-ref declaration, matches the same name in the binding XML file.
CWNEN0018E: The {0} injection target is specified in an annotation that does not exist in the XML deployment descriptor.
Problem The following information is stated in the EJB specification overriding rules: When an injection target is already present and is specified using XML, the annotation injection target must specify the same field or property method.
User response Change the annotation injection target to match the previously defined XML injection target of the same field or property method.
CWNEN0019E: The {0} injection target field must not be declared final.
Problem According to the EJB specification, an injection target field must not be declared final.
User response Correct either the field name or field signature to specify one of the non-private class fields.
CWNEN0020E: The injection engine caught the following security exception when it attempted to access the {1} member: {0}.
Problem The injection engine did not have the proper security credentials to access the member.
User response Take action based on the message that is associated with exception.
CWNEN0021W: The {0} field is declared as {1} but the requested injection type for the field is {2}.
Problem The field type indicated on the injection target is not correct.
User response Ensure that the annotation or injection target XML is specifying the intended field.
CWNEN0022E: The injection engine cannot find the{0} member on the {1} class.
Problem The class does not have a field value with the specified member name.
User response Ensure that the field is spelled correctly and that the class contains the field.
CWNEN0023E: One or more of the following arguments is null: {0} targetClass, {1} targetName, {2} injectionClass.
Problem The injection engine encountered an error when it attempted to use the injection target information that is specified in the XML code.
User response Ensure that the XML, which exists in the deployment descriptor, is correct.
CWNEN0024E: The injection engine failed to load the {0} ObjectFactory class.
Problem The injection engine failed to load and instantiate the specified object class.
User response Ensure that the class is available and that the constructor is visible and accessible.
CWNEN0025W: The enterprise bean is being bound to an empty string in the global Java Naming and Directory Interface (JNDI) namespace.
Problem The information annotation or injection target is incorrect or incomplete.
User response Ensure that the annotation or injection target XML for the enterprise bean is correct.
CWNEN0026E: The {0} enterprise bean home and remote, or local-home and local elements, are either missing or cannot be resolved.
Problem The home and remote, or local-home and local elements, are either missing or cannot be resolved.
User response Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor.
CWNEN0027E: The injection engine caught the following naming exception {0} when attempting to bind {1} into the global Java Naming and Directory Interface (JNDI) namespace.
Problem The injection engine encountered an exception when it attempted to bind .
User response Take action based upon message associated with exception.
CWNEN0028E: The injection engine encountered an error injecting {0} into {1}
Problem The type specified is not injectable into the class specified.
User response Ensure that the annotation or injection target XML for the enterprise bean is correct.
CWNEN0029E: The injection engine encountered an error injecting {0} into {1}. The {0} type may only be injected into a {1} enterprise bean.
Problem Only EJBContext or TimerService objects may be injected directly into an enterprise bean.
User response Ensure that the type specified is a EJBContext or TimerService object.
CWNEN0030E: The {0} factory encountered a problem getting the object instance {1} binding object.
Problem The object factory specified is incorrect for the binding object.
User response Ensure the factory has an object bound correctly.
CWNEN0031E: A failure occured creating {0} reference of {1} type.
Problem A problem was encountered creating a reference to be found into the global Java Naming and Directory Interface (JNDI) namespace.
User response Ensure the reference specified is correct.
CWNEN0032E: Failed to process the XML for {0} {1}
Problem The XML for the specified reference is incorrect or incomplete.
User response Ensure that the XML, which exists in the deployment descriptor, is correct.
CWNEN0033W: The {0} interface, which is specified for the <ejb-ref> or <ejb-local-ref> tags, cannot be found.
Problem The interface class either is missing or cannot be found.
User response Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available.
CWNEN0034E: The ejb-link/beanName is specified incorrectly. The {0} bean : {1} module name must end with .jar
Problem The information annotation or injection target is incorrect or incomplete.
User response Ensure that the annotation or injection target XML for the enterprise bean is correct.
CWNEN0035E: The injection engine was unable to resolve injection object. A {0} reference was expected.
Problem The reference object was specified incorrectly.
User response Ensure that the injection object specified is correct.
CWNEN0036E: The {0} binding object is not a Reference.
Problem The object specified is inccorrect.
User response Ensure the object is set to a type Reference.
CWNEN0037E: The {0} factory is not for creating a Reference for {1} binding object.
Problem The factory was incorrectly specified.
User response Specify a factory for the binding object being used.
CWNEN0038E: The address for {0} Reference is empty (null).
Problem A name of the RefAddr for the Reference was not specified.
User response Specicfy a RefAddr for the Reference.
CWNEN0039E: The {0} interface that is specified for the <ejb-ref> or <ejb-local-ref> tags cannot be found.
Problem The interface class either is missing or cannot be found.
User response Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available.
CWNEN0040W: The {0} field or method was configured to be injected multiple times.
Problem When multiple injection targets are configured for the same field or method, the injection engine is not able to determine which target to inject.
User response Do not configure the same field or method with multiple injection targets.
CWNEN0041E: The {0} enterprise bean in {1} module with the {2} interface cannot be found on this node.
Problem The scope of AutoLink is limited to the application in which the EJB reference occurs, and to servers that are not members of a Application Server cluster.
User response Verify that the enterprise beans, which are being referenced, exist in the same application.
CWNEN0042W: The {0} env-entry statement is already specified with the {1} type.
Problem Duplicate env-entry statements with the same name are not allowed.
User response Do not configure an env-entry with the same name.
CWNEN0043E: Injecting a UserTransaction interface into a container managed transaction bean is not allowed.
Problem The Enterprise JavaBeans (EJB) specification requires that the UserTransaction interface is unavailable to enterprise beans with container-managed transaction demarcation.
User response Do not to inject a UserTransaction interface into a container managed transaction bean.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.wsspi.injectionengine.injection.html

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