CWNEN

Express (Distributed operating systems), v8.0 > Reference > Messages

CWNEN

CWNEN0005E: The injection engine service is not available.

Explanation The injection engine service for the specified server is not available.
Action The injection engine service is started as a singleton service on all application server processes. Check that the application server started without any errors.

CWNEN0006E: The injection engine cannot register the injection processors until the injection engine service is initialized.

Explanation 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 registered with the injection engine.
Action 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.

Explanation The method for the injection target must be a setter property method.
Action 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.

Explanation There was an error when processing the meta data in the deployment descriptor.
Action Ensure that the XML contained in deployment descriptor is correct.

CWNEN0010E: The injection engine failed to process the {0} or {1} annotation in the {2} class.

Explanation The injection engine was unable to properly set up the injection targets for the specified class.
Action 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.

Explanation The bindings and injection information contain errors.
Action Ensure that the annotations contained in the class and XML contained in deployment descriptor is correct.

CWNEN0012E: The injection engine failed to initialize the {0} processor.

Explanation The processor failed to initialize.
Action Ensure that the processor is available and properly registered with the injection engine.

CWNEN0013W: The following NumberFormatException exception occurred when the injection engine attempted to convert the {0} <env-entry-name> {1} <env-entry-value>: {2}

Explanation The container cannot process an environment entry due to a NumberFormatException exception.
Action 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.

Explanation 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.
Action 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}

Explanation The injection engine encountered an exception when it attempted to create a java:comp/env entry.
Action Take action based upon message associated with exception.

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.

Explanation The injection engine encountered a type that is not valid for an environment entry.
Action Ensure that you use one of following environment entry types: String, Character, Byte, Short, Integer, Long, Boolean, Double, Float, Class, and any subclass of Enum.

CWNEN0017E: The injection engine cannot resolve the target of the {0} resource-ref declaration to the associated binding location in the global namespace.

Explanation 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 JNDI namespace.
Action 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.

Explanation 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.
Action 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.

Explanation According to the EJB specification, an injection target field must not be declared final.
Action 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}.

Explanation The injection engine did not have the proper security credentials to access the member.
Action 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}.

Explanation The field type indicated on the injection target is not correct.
Action Ensure that the annotation or injection target XML is specifying the intended field.

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.

Explanation The class does not have a method or field with the configured injection target property name.
Action Ensure that the configured injection target property name is spelled correctly and that the class contains the corresponding field or property method.

CWNEN0023E: One or more of the following arguments is null: {0} targetClass, {1} targetName, {2} injectionClass.

Explanation The injection engine encountered an error when it attempted to use the injection target information specified in the XML code.
Action Ensure that the XML, which exists in the deployment descriptor, is correct.

CWNEN0024E: The injection engine failed to load the {0} ObjectFactory class.

Explanation The injection engine failed to load and instantiate the specified object class.
Action 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 JNDI namespace.

Explanation The information annotation or injection target is incorrect or incomplete.
Action 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.

Explanation The home and remote, or local-home and local elements, are either missing or cannot be resolved.
Action 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 JNDI namespace.

Explanation The injection engine encountered an exception when it attempted to bind .
Action Take action based upon message associated with exception.

CWNEN0028E: The injection engine encountered an error injecting {0} into {1}

Explanation The type specified is not injectable into the class specified.
Action 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.

Explanation Only EJBContext or TimerService objects may be injected directly into an enterprise bean.
Action 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.

Explanation The object factory specified is incorrect for the binding object.
Action Ensure the factory has an object bound correctly.

CWNEN0031E: A failure occurred creating {0} reference of {1} type.

Explanation A problem was encountered creating a reference to be found into the global JNDI namespace.
Action Ensure the reference specified is correct.

CWNEN0032E: Failed to process the XML for {0} {1}

Explanation The XML for the specified reference is incorrect or incomplete.
Action 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.

Explanation The interface class either is missing or cannot be found.
Action 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 or .war.

Explanation The information annotation or injection target is incorrect or incomplete.
Action Ensure that the annotation or injection target XML for the enterprise bean is correct.

CWNEN0035E: The {0} reference of type {1} for the {2} component in the {3} module of the {4} application cannot be resolved.

Explanation The application declared a reference to an object which could not be found.
Action Look for a previous message that indicates why the referenced object could not be found, and verify the configuration for the reference is correct.

CWNEN0036E: The {0} binding object is not a Reference.

Explanation The object specified is incorrect.
Action Ensure the object is set to a type Reference.

CWNEN0037E: The {0} factory is not for creating a Reference for {1} binding object.

Explanation The factory was incorrectly specified.
Action Specify a factory for the binding object being used.

CWNEN0038E: The address for {0} Reference is empty (null).

Explanation A name of the RefAddr for the Reference was not specified.
Action Specify a RefAddr for the Reference.

CWNEN0039E: The {0} interface specified for the <ejb-ref> or <ejb-local-ref> tags cannot be found.

Explanation The interface class either is missing or cannot be found.
Action 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.

Explanation When multiple injection targets are configured for the same field or method, the injection engine is not able to determine which target to inject.
Action Do not configure the same field or method with multiple injection targets.

CWNEN0041E: The {0} EJB reference in the {1} module to the {2} interface of the {3} enterprise bean cannot be resolved on this node.

Explanation 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.
Action 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.

Explanation Duplicate env-entry statements with the same name are not allowed.
Action Do not configure an env-entry with the same name.

CWNEN0043E: Injecting a UserTransaction interface into a container managed transaction bean is not allowed.

Explanation The EJB specification requires that the UserTransaction interface is unavailable to enterprise beans with container-managed transaction demarcation.
Action Do not to inject a UserTransaction interface into a container managed transaction bean.

CWNEN0044E: A resource reference binding could not be found for the {0} resource reference, defined for the {1} component.

Explanation A binding for the resource reference may have been omitted or specified incorrectly.
Action A resource reference is defined for a component with the @Resource annotation in a component class file, or one of the following XML stanzas in the deployment descriptor : resource-env-ref, resource-ref, message-destination-ref. Ensure that a binding is defined for the resource reference in the ibm-ejb-jar-bnd file if the component is an enterprise Java bean (EJB) module, ibm-web-bnd file if the component is a web application module, or ibm-application-client-bnd file if the component is a client module.

CWNEN0045W: The env-entry {0} defined for the {1} component has no injection target or value specified.

Explanation A value for an env-entry must be specified if the injection-target value is not set.
Action Specify a value, injection-target, or both for the env-entry.

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.

Explanation The type of the resource identified by the resource reference binding cannot be checked for compatibility with the type defined on one of the following XML stanzas in the deployment descriptor : resource-env-ref, resource-ref, message-destination-ref.
Action Change the type declared for the resource reference in the deployment descriptor to a type that may be loaded.

CWNEN0047W: Resource annotations on the fields of the {0} class will be ignored. The annotations could not be obtained because of the exception : {1}

Explanation The application will not function properly if the specified class is used.
Action The class should either be removed from the application, or the cause of the exception corrected.

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}

Explanation The application will not function properly if the specified class is used.
Action The class should either be removed from the application, or the cause of the exception corrected.

CWNEN0049W: Resource annotations on the methods of the {0} class will be ignored. The annotations could not be obtained because of the exception : {1}

Explanation The application will not function properly if the specified class is used.
Action The class should either be removed from the application, or the cause of the exception corrected.

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}

Explanation The application will not function properly if the specified class is used.
Action The class should either be removed from the application, or the cause of the exception corrected.

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}.

Explanation When multiple resource references are defined in the XML deployment descriptor for the same component namespace with the same name, the type of the resource must be the same. A typical scenario where this may occur is when defining resource references for an EJB and for a corresponding interceptor class. Both the EJB and the interceptor share the same component namespace, so resource references that are common between the two must be the same type.
Action In the XML deployment descriptor, change the name of one of the resource references, or change the type of one of the references to match the other one.

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}.

Explanation When multiple resource references are defined in the XML deployment descriptor for the same component namespace with the same name, all attributes of the resource must either be the same, or one must be assignable to the other. A typical scenario where this may occur is when defining resource references for an EJB and for a corresponding interceptor class. Both the EJB and the interceptor share the same component namespace, so resource references that are common between the two must be compatible.
Action In the XML deployment descriptor, change the name of one of the resource references, or change one of the conflicting values so they are the same value or one is assignable to the other.

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}.

Explanation When multiple resource references are defined in the XML deployment descriptor and in source code annotations for the same component namespace with the same name, some attributes of the resource must either be the same, or one must be assignable to the other.
Action In the XML deployment descriptor or source code annotations, change the name of one of the resource references, or change one of the conflicting values so they are the same value or one is assignable to the other.

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}.

Explanation When multiple resource references are defined in source code annotations for the same component namespace with the same name, all attributes of the resource must either be the same, or one must be assignable to the other.
Action In the source code annotations, change the name of one of the resource references, or change one of the conflicting values so they are the same value or one is assignable to the other.

CWNEN0055E: The {0} message destination in the {1} module of the {2} application cannot be found on this node.

Explanation The scope of AutoLink is limited to the application in which the message destination reference occurs, and to servers that are not members of an Application Server cluster.
Action Verify that the message destination, which is being referenced, exists in the same application. Or, define a binding for the message destination.

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.

Explanation Requesting injection of a resource into both a property instance variable and its corresponding set method is an error.
Action Remove one of the annotations from either the field or method. Either the field or the method could request injection of a resource of a different (non-default) name. By explicitly specifying the JNDI name of a resource, a single resource may be injected into multiple fields or methods of multiple classes.

CWNEN0057W: The {0}.{1} injection target must not be declared static.

Explanation According to the EJB specification, an injection target may only be declared static if it exists in the client container.
Action Either change the code for the injection target to be non-static, choose a different injection target, or remove the injection target and populate it manually.

CWNEN0058E: The {0}.{1} injection target must be declared static in the client container.

Explanation According to the EJB specification, an injection target in the client container must be declared static.
Action Either change the code for the injection target to be static, choose a different injection target, or remove the injection target and populate it manually.

CWNEN0059E: The Injection Engine failed to inject the {0} binding object into the {1}:{2} EJB file because the attempted injection is recursive or cyclic.

Explanation A cyclic or recursive injection occurs when the injection of one object requires another injection of the same object. For example, this scenario can occur when a stateful session bean attempts to inject an instance of the same type into itself.
Action Modify the application code or configuration so that injection targets do not depend on themselves either directly or indirectly.

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.

Explanation The class was configured to have a UserTransaction instance injected into it, which is not allowed. If the class is a bean, then the bean is not configured for bean-managed transactions. If the class is an interceptor or Web service handler, then it is used by one or more beans that are not configured for bean-managed transactions.
Action Change the class to stop injecting a UserTransaction instance, or change the bean configuration to allow bean-managed transactions. If this class is an interceptor or Web service handler class used by multiple beans, some of which are configured for bean-managed transactions and others which are not, then create a new interceptor or Web service handler class that does not inject a UserTransaction instance and use it with the beans that are configured for container-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.

Explanation The class was configured to have method injection, but multiple methods are compatible with the type of the object to be injected.
Action Change the bean configuration to specify the exact type of one of the methods, change the class to have a method with a parameter type that is exactly the same as the type of the injection configuration, or change the class by removing or renaming one of the ambiguous methods.

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}.

Explanation When a reference with the same name is defined by several components that share a component namespace, all binding and extension properties of the reference must be the same.
Action In the binding or extension file of the module, change one of the conflicting values so they are the same.

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}.

Explanation A simple environment entry for an enterprise module of the Enum type must be assigned a valid Enum identifier value.
Action Change the simple environment entry of the Enum type to a valid Enum identifier value.

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}.

Explanation A simple environment entry for an enterprise module might be one of the following Java types: String, Character, Byte, Short, Integer, Long, Boolean, Double, Float, Class, and any subclass of Enum.
Action Change the simple environment entry to one of the supported types.

CWNEN0065E: The {0} reference for the {1} component in the {2} module in the {3} application has a name that is not valid.

Explanation Reference names must either be relative to java:comp/env or start with java:global, java:app, java:module, or java:comp.
Action Change the reference name in the deployment descriptor and source code annotations.

CWNEN0066E: The @DataSourceDefinition source code annotation with the {0} name attribute for the {1} component in the {2} module in the {3} application has the following configuration data for the properties attribute that is not valid: {4}

Explanation The format for properties specified in the DataSourceDefinition annotation is name=value.
Action Change the properties attribute in the source code annotation to have the name=value format.

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}

Explanation The isolationLevel must be one of the following constants from the java.sql.Connection class: TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, or TRANSACTION_SERIALIZABLE.
Action Change the isolationLevel attribute in the source code annotation to one of the valid values.

CWNEN0068E: The {0} EJB reference in the {1} module to the {2} interface of an enterprise bean cannot be resolved on this node.

Explanation 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.
Action Verify that the enterprise beans, which are being referenced, exist in the same application.

CWNEN0069E: The {0}.{1} injection method must be declared with exactly one parameter, not {2} parameters.

Explanation Injection methods must follow the conventions of JavaBeans property set methods.
Action Either change the code for the injection method to have exactly one parameter, choose a different injection target, or remove the injection target and populate the value manually.

CWNEN0070W: The {0} annotation class will not be recognized because it was loaded from the {1} location rather than from a product class loader.

Explanation The application class loader or an application server class loader has loaded an annotation class that should have been loaded by a product class loader. This occurs when a class loader has been configured to load classes with the local class loader first (parent last). The annotation will only be recognized if it is loaded by a product class loader.
Action Remove the annotation class from the application or application server class path.

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}

Explanation The specified attribute must either be unspecified or have the default value.
Action Remove the attribute from the source code annotation or deployment descriptor.

CWNEN8990I: This message is an English-only Informational message: {0}.

Explanation This informational message is not translated.
Action See message for details.

CWNEN8991W: This message is an English-only Warning message: {0}.

Explanation This warning message is not translated.
Action See message for details.

CWNEN8992E: This message is an English-only Error message: {0}.

Explanation This error message is not translated.
Action See message for details.

+
Search Tips | Advanced Search

Explanation	The injection engine service for the specified server is not available.
Action	The injection engine service is started as a singleton service on all application server processes. Check that the application server started without any errors.

Explanation	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 registered with the injection engine.
Action	Ensure that the injection processors are being registered after the application server is started.

Explanation	The method for the injection target must be a setter property method.
Action	Ensure that the annotation or injection target XML is specifying the intended method.

Explanation	There was an error when processing the meta data in the deployment descriptor.
Action	Ensure that the XML contained in deployment descriptor is correct.

Explanation	The injection engine was unable to properly set up the injection targets for the specified class.
Action	Ensure that the correct annotations are contained within the class and within the XML in the deployment descriptor.

Explanation	The bindings and injection information contain errors.
Action	Ensure that the annotations contained in the class and XML contained in deployment descriptor is correct.

Explanation	The processor failed to initialize.
Action	Ensure that the processor is available and properly registered with the injection engine.

Explanation	The container cannot process an environment entry due to a NumberFormatException exception.
Action	Ensure that the value for the environment entry is a valid string representation for the specified type.

Explanation	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.
Action	Change the java:comp/env context environment entry of the Boolean type to either a true or false value.

Explanation	The injection engine encountered an exception when it attempted to create a java:comp/env entry.
Action	Take action based upon message associated with exception.

Explanation	The injection engine encountered a type that is not valid for an environment entry.
Action	Ensure that you use one of following environment entry types: String, Character, Byte, Short, Integer, Long, Boolean, Double, Float, Class, and any subclass of Enum.

Explanation	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 JNDI namespace.
Action	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.

Explanation	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.
Action	Change the annotation injection target to match the previously defined XML injection target of the same field or property method.

Explanation	According to the EJB specification, an injection target field must not be declared final.
Action	Correct either the field name or field signature to specify one of the non-private class fields.

Explanation	The injection engine did not have the proper security credentials to access the member.
Action	Take action based on the message that is associated with exception.

Explanation	The field type indicated on the injection target is not correct.
Action	Ensure that the annotation or injection target XML is specifying the intended field.

Explanation	The class does not have a method or field with the configured injection target property name.
Action	Ensure that the configured injection target property name is spelled correctly and that the class contains the corresponding field or property method.

Explanation	The injection engine encountered an error when it attempted to use the injection target information specified in the XML code.
Action	Ensure that the XML, which exists in the deployment descriptor, is correct.

Explanation	The injection engine failed to load and instantiate the specified object class.
Action	Ensure that the class is available and that the constructor is visible and accessible.

Explanation	The information annotation or injection target is incorrect or incomplete.
Action	Ensure that the annotation or injection target XML for the enterprise bean is correct.

Explanation	The home and remote, or local-home and local elements, are either missing or cannot be resolved.
Action	Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor.

Explanation	The type specified is not injectable into the class specified.
Action	Ensure that the annotation or injection target XML for the enterprise bean is correct.

Explanation	Only EJBContext or TimerService objects may be injected directly into an enterprise bean.
Action	Ensure that the type specified is a EJBContext or TimerService object.

Explanation	The object factory specified is incorrect for the binding object.
Action	Ensure the factory has an object bound correctly.

Explanation	A problem was encountered creating a reference to be found into the global JNDI namespace.
Action	Ensure the reference specified is correct.

Explanation	The XML for the specified reference is incorrect or incomplete.
Action	Ensure that the XML, which exists in the deployment descriptor, is correct.

Explanation	The interface class either is missing or cannot be found.
Action	Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available.

Explanation	The application declared a reference to an object which could not be found.
Action	Look for a previous message that indicates why the referenced object could not be found, and verify the configuration for the reference is correct.

Explanation	The object specified is incorrect.
Action	Ensure the object is set to a type Reference.

Explanation	The factory was incorrectly specified.
Action	Specify a factory for the binding object being used.