[jboss-jira] [JBoss JIRA] (WFLY-1705) JPA persistence units make use of SerializableValidatorFactory instead of using the JNDI bound default ValidatorFactory
[
https://issues.jboss.org/browse/WFLY-1705?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-1705:
------------------------------------
I created a pull request https://github.com/wildfly/wildfly/pull/5027 to bring the jipi-18
change in.
I also pushed changes to help with WFLY-1705 to
https://github.com/scottmarlow/wildfly/tree/WFLY-1705. Let me know if you want me to push
them or if you want to merge in with your local branch changes. To bring my changes into
your local git repo, you would do:
{quote}
git fetch https://github.com/scottmarlow/wildfly.git WFLY-1705:WFLY-1705
{quote}
You could then rebase or cherry-pick the changes in (depending on whether WFLY-2032 is
merged to github master yet or not). Do a "git log WFLY-1705" after running the
above to see the commits.
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