CWNBV

CWNBV0001E: During server start the BeanValidationService failed to register with the injection service. Applications requiring injection of either a ValidatorFactory class or a Validator class will fail. The following error occurred: {0}.

Explanation

The BeanValidationService failed to register with the injection engine when the application server started. The failure is unexpected. A possible cause is that the injection service has not been started.

Action

Correct any previous errors and ensure that the injection service has been started. If the injection service is available and you continue to have the problem, see the problem determination information. This information is available on the WebSphere Application Server Support web page at http://www.ibm.com/software/webservers/appserv/was/support.

CWNBV0002E: The BeanValidationService is unable to create a ValidatorFactory class.

Explanation

The BeanValidationService is unable to create a validator factory. The failure is unexpected. See the description of the specified exception for more information. The problem might be caused by the validation.xml file that is provided with the application.

Action

Ensure that the provided validation.xml file is valid and the specified default validation provider, message interpolator or traversable resolver are available in the class path. If the validation.xml file is valid and the proper information is available in the class path but you continue to have the problem, see the problem determination information. This information is available on the WebSphere Application Server Support web page at http://www.ibm.com/software/webservers/appserv/was/support.

CWNBV0003E: The BeanValidationService is unable to create a ValidationFactory class because it was unable to load or instantiate the class: {0} in path {1} because of error: {2}

Explanation

The BeanValidationService is unable to load or instantiate the class used to create the ValidationFactory. The problem might exist because the class does not exist or the class is not available in the application class path.

Action

Ensure that the class is available and on the application class path. If class is valid and available in the class path but you continue to have the problem, see the problem determination information. This information is available on the WebSphere Application Server Support web page at http://www.ibm.com/software/webservers/appserv/was/support.

CWNBV0004E: An incorrect syntax or error is detected in the validation.xml file found in {0}. The following associated error message occurred: {1}

Explanation

The validation.xml file contains errors and does not conform to the schema definition.

Action

Correct the errors in the validation.xml file and try again.

CWNBV0005W: A validation.xml file was found for the {0} module. However, that validation.xml file is not configured for validation; therefore this XML file is ignored.

Explanation

The BeanValidationService cannot create a ValidatorFactory because of an error parsing the validation.xml file with the validation-configuration-1.0.xsd schema file. This error may indicate that the validation.xml file is not intended for use by the Bean Validation run-time; therefore, this XML file is ignored.

Action

If the validation.xml file is not for creating a ValidatorFactory instance, then ignore the message. However if the validation.xml file is intended to create a ValidatorFactory instance, then a problem exists. Enable Bean Validation run-time trace in the application server, stop the application, restart the application, and examine the trace output file for a trace event such as: Unexpected exception when trying to unmarshall the validation.xml file. Examine the exception stack trace for debugging assistance.

CWNBV0006E: 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.

Explanation

JNDI operations on a java:comp/env name are only supported on threads associated with a Java EE application component.

Action

Modify the application so that the JNDI operation occurs on a thread associated with a Java EE application component.

CWNBV0007E: @ValidateOnExecution is not allowed on methods that override a superclass method or implement an interface. Check configuration for {0}

Explanation

@ValidateOnExecution is not allowed on methods that override a superclass method or implement an interface. A method that overrides a superclass method or implements an interface method inherits the behavior of the method that it overrides or implements.

Action

Remove the @ValidateOnExecution from the specified method.

CWNBV0008E: Mixing IMPLICIT type with other executable types is not allowed. Check the executable types set for: {0}

Explanation

According to the Bean Validation Specification, mixing IMPLICIT type with other executable types is not allowed for the @ValidateOnExecution annotation.

Action

Update the method, class, or global XML settings for executable types to prevent mixing IMPLICIT type with other executable types.

CWNBV0200W: The Hibernate Validator CDI extension for the {0} application cannot be registered, so CDI integration for Bean Validation is not available for this application. The following issue occurred while the CDI extension was being registered: {1}

Explanation

A CDI extension is provided for the built-in Bean Validation provider (Hibernate Validator), which is only supported when the built-in ValidationProvider is used and the validation.xml for the application is valid.

Action

See the root issue at the end of the message. Likely causes include invalid content in META-INF/validation.xml or a <default-provider> other than the org.hibernate.validator.HibernateValidator provider.