[jboss-jira] [JBoss JIRA] (WFLY-13734) JPA subsystem should fail deployment if ValidationMode.CALLBACK is configured but the BV capability is not present

[ https://issues.redhat.com/browse/WFLY-13734?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13734: ------------------------------------- {quote} If the user excludes the bean-validation Galleon layer from jpa / jpa-distributed Galleon layers, and configures JPA with ValidationMode.CALLBACK, the deployment will fail because the persistent provider will thrown an exception. {quote} Correct, they will then either include bean-validation Galleon layer from jpa / jpa-distributed Galleon layers or stop using BeanValidation by switching to ValidationMode.NONE. {quote} Scott Marlow just wanted to confirm the following, I assume the JPA persistent provider is able to distinguish which ValidationMode has been configured, is this assumption correct? {quote} Yes, the JPA persistence provider is passed the same (javax.persistence.spi.PersistenceUnitInfo) "pu" variable which means the persistence provider can also call pu.getValidationMode() (it is also passed a "javax.persistence.validation.factory" property only if non-null). {quote} There is no distinction between the value the validatorFactory gets, it will be always null, when we don't have the "org.wildfly.bean-validation" capability and we are using either ValidationMode.CALLBACK or ValidationMode.AUTO. So the persistent provider should know that the configuration is ValidationMode.CALLBACK to throwing an exception. {quote} Correct, the persistence provider is responsible for throwing the exception for ValidationMode.CALLBACK and null validatorFactory. -- This message was sent by Atlassian Jira (v7.13.8#713008)