[
https://issues.jboss.org/browse/WFLY-1705?page=com.atlassian.jira.plugin....
]
Farah Juma commented on WFLY-1705:
----------------------------------
Jaikiran explained that in these tests, the EJB remote client issues a transaction commit
message to the server. The server then handles the commit on the transaction. The commit
happens outside of the deployment's context. This is why the TCCL isn't set to the
deployment's classloader.
Setting the TCCL to the deployment's classloader in
LazyValidatorFactory.usingContext() solves the problem.
I've now created the following pull request:
https://github.com/wildfly/wildfly/pull/5123
JPA persistence units make use of SerializableValidatorFactory
instead of using the JNDI bound default ValidatorFactory
-----------------------------------------------------------------------------------------------------------------------
Key: WFLY-1705
URL:
https://issues.jboss.org/browse/WFLY-1705
Project: WildFly
Issue Type: Feature Request
Components: EE, JPA / Hibernate
Affects Versions: 8.0.0.Alpha2
Reporter: Hardy Ferentschik
Assignee: Farah Juma
I think there is no need for {{SerializableValidatorFactory}}. _LazyValidatorFactory_
should be used at all times to also ensure that CDI injection works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira