[
http://opensource.atlassian.com/projects/hibernate/browse/HV-98?page=com....
]
Hardy Ferentschik commented on HV-98:
-------------------------------------
Right, configuration settings including the mapping streams are provided by the
{{ConfigurationState}} instance. Also the streams will be closed after the factory will be
created.
One way to reload the configuration of the {{ValidatorFactory}} would be to clear the
caches and provide a new {{ConfigurationState}}. But what happens if the
{{ValidationProvider}} in {{validation.xml}} has changed? Is it not better to just create
a new ValidatorFactory? Do we have a concrete usecase?
Investigate the possibiltiy to dynamically reload the meta data
---------------------------------------------------------------
Key: HV-98
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-98
Project: Hibernate Validator
Issue Type: New Feature
Components: engine
Reporter: Emmanuel Bernard
Priority: Minor
Fix For: 4.1.0
- Test how a dynamic reloading mode would work.
- Instead of caching metadata by ValidationFactory, reload as the data might have changed
(annotations or XML)
- This can be a configuration setting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira