[ https://issues.jboss.org/browse/AS7-3652?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-3652: ----------------------------------- Looks like this depends on Bean Validation APIs. When I added support to use the Endpoint for activate/deactivate here https://github.com/jaikiran/jboss-as/compare/jca-endpoint I start seeing exceptions during MDB deployment: {code} Caused by: javax.validation.ValidationException: Unable to find a default provider at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264) at org.jboss.jca.core.bv.BeanValidationUtil.createValidatorFactory(BeanValidationUtil.java:51) at org.jboss.jca.core.bv.BeanValidationUtil.createValidator(BeanValidationUtil.java:63) at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:84) at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:161) at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more {code} I'll check with Jesper about this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira