[hibernate-issues] [Hibernate-JIRA] Commented: (HV-460) Create a SerializableValidatorFactory wrapper that has enough information to either access or create a matching implementation when deserializing

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-460?page=com... ] Hardy Ferentschik commented on HV-460: -------------------------------------- {quote} Our current workaround is to share the same Validator Factory instance but a user just reported a problem with that (http://community.jboss.org/thread/174014). {quote} Right, there is a problem. _ValidatorFactoryImpl_ uses a _BeanMetaDataManager_ which in turn uses _BeanMetaDataCache_. The cache caches the Bean Validation metadata per class to speed up validation. Depending on how exactly the class loading works regarding re-deploys this will cause a problem. {quote} I'm thinking that we should instead create a separate Validator Factory per EntityManagerFactory (so each application will have its own factory for each persistence unit). This is easy for standalone applications. For clustered applications, will be a bit harder (but doable). {quote} Right, that is the way to go without modifying Validator. I wonder what we can/should do from our side to prevent this. Obviously serializing will help, but maybe we can offer other solutions as well. {quote} Could you confirm that each application should have its own instance of a ValidatorFactory? {quote} AS things stands atm, yes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira