[hibernate-dev] WildFly BeanValidationCdiIntegrationTestCase test failure with ORM 5

[Hardy Ferentschik]

On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
> Hardy,
> 
> It seems that the ValidatorFactoryBean#createConstraintValidatorFactory is
> getting called too late for some reason. http://pastebin.com/WrdD91Hr shows
> the call stack for
> ValidatorFactoryBean#create(CreationalContext<ValidatorFactory> ctx) which
> calls createConstraintValidatorFactory, which seems too late
> (CdiValidatorFactoryService is shutting down).

Did you not change some of the integration code in order to upgrade to ORM 5
within Wildfly? It is not just a version upgrade, right? 

The reason I am asking is that afaik we jump through quite some hoops regarding
the Bean Validation integration to ensure that the JNDI bound Validator(Factory)
is CDI enabled and identical to the one which can be retrieved via CDI. This
is the whole LazyValidatorFactory stuff. I am not so familiar with this code,
but I am wondering whether your changes for the ORM 5 integration interfere with
the Bean Valiadtion bootstrapping. What needed to change for the ORM 5 integration?
I know that you and Sanne discussed the ability to bootstrap the PersistenceProvider
using the API as defined by JPA. Did you go in this direction?

> To recreate the WildFly ORM 5 issue on WildFly (if you want to see it
> yourself), steps are:

Ok, I'll take a look at your branch.

Is this test failure the last hurdle to integrate ORM5 into Wildfly 10?

--Hardy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 496 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hibernate-dev/attachments/20150708/d1298f38/attachment.bin