CWNEN

CWNEN0005E: The injection engine service is not available.
CWNEN0006E: The injection engine cannot register the injection processors until the injection engine service is initialized.
CWNEN0008E: The {0} method must be a setter method; the annotation is ignored.
CWNEN0009E: The injection engine failed to process the XML code from the deployment descriptor due to the following error: {0}
CWNEN0010E: The injection engine failed to process the {0} or {1} annotation in the {2} class.
CWNEN0011E: The injection engine failed to process bindings for the metadata due to the following error: {0}
CWNEN0012E: The injection engine failed to initialize the {0} processor.
CWNEN0013W: The following NumberFormatException exception occurred when the injection engine attempted to convert the {0} <env-entry-name> {1} <env-entry-value>: {2}
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.
CWNEN0015W: The following exception has been caught in attempting to construct the {0} <env-entry-name> {1} <env-entry-value>: {2}
CWNEN0016W: The {0} type, which is not valid, has been specified for the {1} simple environment entry in the {2} component of the {3} module.
CWNEN0017E: The injection engine cannot resolve the target of the {0} resource-ref declaration to the associated binding location in the global namespace.
CWNEN0018E: The {0} injection target is specified in an annotation that does not exist in the XML deployment descriptor.
CWNEN0019E: The {0} injection target field must not be declared final.
CWNEN0020E: The injection engine caught the following security exception when it attempted to access the {1} member: {0}.
CWNEN0021W: The {0} field is declared as {1} but the requested injection type for the field is {2}.
CWNEN0022E: An injection target for the {0} reference cannot be processed because neither the {1} method nor the {2} field exist on the {3} class.
CWNEN0023E: One or more of the following arguments is null: {0} targetClass, {1} targetName, {2} injectionClass.
CWNEN0024E: The injection engine failed to load the {0} ObjectFactory class.
CWNEN0025W: The enterprise bean is being bound to an empty string in the global Java Naming and Directory Interface (JNDI) namespace.
CWNEN0026E: The {0} enterprise bean home and remote, or local-home and local elements, are either missing or cannot be resolved.
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.
CWNEN0028E: The injection engine encountered the following error injecting {0} into {1}: {2}
CWNEN0029E: The injection engine encountered an error injecting {0} into {1}. The {0} type may only be injected into a {1} enterprise bean.
CWNEN0030E: The server was unable to obtain an object instance for the {0} reference. The exception message was: {1}
CWNEN0031E: A failure occurred creating {0} reference of {1} type.
CWNEN0032E: Failed to process the XML for {0} {1}
CWNEN0033W: The {0} interface, which is specified for the <ejb-ref> or <ejb-local-ref> tags, cannot be found.
CWNEN0034E: The ejb-link/beanName is specified incorrectly. The {0} bean : {1} module name must end with .jar or .war.
CWNEN0035E: The {0} reference of type {1} for the {2} component in the {3} module of the {4} application cannot be resolved.
CWNEN0036E: The {0} binding object is not a Reference.
CWNEN0037E: The {0} factory is not for creating a Reference for {1} binding object.
CWNEN0038E: The address for {0} Reference is empty (null).
CWNEN0039E: The {0} interface that is specified for the <ejb-ref> or <ejb-local-ref> tags cannot be found.
CWNEN0040W: The {0} field or method was configured to be injected multiple times.
CWNEN0041E: The {0} EJB reference in the {1} module to the {2} interface of the {3} enterprise bean cannot be resolved on this node.
CWNEN0042W: The {0} env-entry statement is already specified with the {1} type.
CWNEN0043E: Injecting a UserTransaction interface into a container managed transaction bean is not allowed.
CWNEN0044E: A resource reference binding could not be found for the {0} resource reference, defined for the {1} component.
CWNEN0045W: The env-entry {0} defined for the {1} component has no injection target or value specified.
CWNEN0046W: The {0} type specified on the resource-ref, resource-env-ref, or message-destination-ref with the {1} name in the {2} module could not be loaded. Compatibility type checking will not be performed for this resource reference.
CWNEN0047W: Resource annotations on the fields of the {0} class will be ignored. The annotations could not be obtained because of the exception : {1}
CWNEN0048W: Resource annotations on the fields of the {0} class will be ignored. The {0} class is being processed for annotations because it is referenced by the {1} application class. The annotations could not be obtained because of the exception : {2}
CWNEN0049W: Resource annotations on the methods of the {0} class will be ignored. The annotations could not be obtained because of the exception : {1}
CWNEN0050W: Resource annotations on the methods of the {0} class will be ignored. The {0} class is being processed for annotations because it is referenced by the {1} application class. The annotations could not be obtained because of the exception : {2}
CWNEN0051E: The {0} bean in the {1} module of the {2} application has conflicting configuration data in the XML deployment descriptor. Conflicting element types exist with the same {3} element value : {4}. The conflicting element types are {5} and {6}.
CWNEN0052E: The {0} bean in the {1} module of the {2} application has conflicting configuration data in the XML deployment descriptor. Conflicting {3} element values exist for multiple {4} elements with the same {5} element value : {6}. The conflicting {3} element values are {7} and {8}.
CWNEN0053E: The {0} bean in the {1} module of the {2} application has conflicting configuration data between the XML deployment descriptor and source code annotations. Conflicting {3} element values or {4} attribute values exist for multiple {5} elements or {6} annotations with the same {7} element value or {8} attribute value : {9}. The conflicting {3} element values or {4} attribute values are {10} and {11}.
CWNEN0054E: The {0} bean in the {1} module of the {2} application has conflicting configuration data in source code annotations. Conflicting {3} attribute values exist for multiple {4} annotations with the same {5} attribute value : {6}. The conflicting {3} attribute values are {7} and {8}.
CWNEN0055E: The {0} message destination in the {1} module of the {2} application cannot be found on this node.
CWNEN0056E: Injection of the {0} resource was specified for both a property instance variable and its corresponding set method on the {1} class in the {2} module of the {3} application.
CWNEN0057W: The {0}.{1} injection target must not be declared static.
CWNEN0058E: The {0}.{1} injection target must be declared static in the client container.
CWNEN0059E: The Injection Engine failed to inject the {0} binding object into the {1}:{2} Enterprise JavaBeans (EJB) file because the attempted injection is recursive or cyclic.
CWNEN0060E: Unable to inject a UserTransaction instance into the {0} class, associated with the {1} component in the {2} module in the {3} application. A UserTransaction instance cannot be injected into this class because it is associated with a bean component that is not configured to allow bean-managed transactions.
CWNEN0061E: The {0} injection target property name for the {1} reference is ambiguous in the {2} class. The {3} method and the {4} method are both type compatible with the {5} type.
CWNEN0062E: The {0} component and the {1} component in the {2} module of the {3} application have conflicting values for the {4} property of the {5} reference. The conflicting values are {6} and {7}.
CWNEN0063E: The {0} simple environment entry in the {1} module of the {2} application, which is the {3} Enum type, is not set to a valid Enum identifier: {4}.
CWNEN0064E: A type, which is not valid, has been specified for the {0} simple environment entry in the {1} module of the {2} application: {3}.
CWNEN0065E: The {0} reference for the {1} component in the {2} module in the {3} application has a name that is not valid.
CWNEN0066E: The {0} source code annotation with the {1} {2} attribute for the {3} component in the {4} module in the {5} application has the following configuration data for the properties attribute that is not valid: {6}
CWNEN0067E: The @DataSourceDefinition source code annotation with the {0} name attribute for the {1} component in the {2} module of the {3} application has the following configuration data for the isolationLevel attribute that is not valid: {4}
CWNEN0068E: The {0} EJB reference in the {1} module to the {2} interface of an enterprise bean cannot be resolved on this node.
CWNEN0069E: The {0}.{1} injection method must be declared with exactly one parameter, not {2} parameters.
CWNEN0070W: The {0} annotation class will not be recognized because it was loaded from the {1} location rather than from a product class loader.
CWNEN0071E: The {0} reference for the {1} component in the {2} module in the {3} application has the {4} type and a value for the {5} attribute that is not valid: {6}
CWNEN0072E: The {0} reference has conflicting values for the {1} attribute: {2} and {3}
CWNEN0073E: The {0} class-level annotation on the {1} class in the {2} module of the {3} application does not specify a JNDI name.
CWNEN0074E: The {0} type of the object instance obtained for the {1} reference is incompatible with the type of the {2} member.
CWNEN0075E: An error occurred while searching in the {0} class for the {1} injection target of the {2} reference of the {3} component in the {4} module in the {5} application: {6}
CWNEN1000E: A JNDI operation on a java:comp/env name cannot be completed because the current thread is not associated with a Java Enterprise Edition application component. This condition can occur when the JNDI client using the java:comp/env name does not occur on the thread of a server application request. Make sure that a Java EE application does not run JNDI operations on java:comp/env names within static code blocks or in threads created by that application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on java:comp/env names.
CWNEN1001E: The object referenced by the {0} JNDI name could not be instantiated. If the reference name maps to a JNDI name in the deployment descriptor bindings for the application performing the JNDI lookup, make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context.
CWNEN1002E: The {0} reference declared by the META-INF/application.xml file in the {1} application is not in the java:global or java:app context.
CWNEN1003E: The server was unable to find the {0} binding with the {1} type for the {2} reference.
CWNEN1004E: The server was unable to find the {0} default binding with the {1} type for the {2} reference.
CWNEN1005E: The server was unable to find the {0} binding with the {1} type for the {2} reference. The binding was specified by the {3} service.
CWNEN1006E: The server was unable to obtain an object for the {0} binding with the {1} type. The exception message was: {2}
CWNEN1007E: The server configuration is missing a feature to support the {0} EJB reference in the {1} component in the {2} module in the {3} application.
CWNEN1008E: The binding contains an indirect lookup that refers to itself.
CWNEN8990I: This message is an English-only Informational message: {0}.
CWNEN8991W: This message is an English-only Warning message: {0}.
CWNEN8992E: This message is an English-only Error message: {0}.