[
https://hibernate.onjira.com/browse/HV-586?page=com.atlassian.jira.plugin...
]
Hardy Ferentschik edited comment on HV-586 at 5/11/12 6:04 AM:
---------------------------------------------------------------
{code}
class A {
@OneToMany
@Valid
@NotEmpty
private Set<B> b;
}
{code}
It could also be that @NotEmpty causes the problem.
was (Author: ztang):
class A {
@OneToMany
@Valid
@NotEmpty
private Set<B> b;
It could also be that @NotEmpty causes the problem.
Hibernate validator initializes lazy proxies
--------------------------------------------
Key: HV-586
URL:
https://hibernate.onjira.com/browse/HV-586
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Final
Environment: CentOs, Glassfish V3
Reporter: Michael G
Priority: Critical
I use hibernate validator for detached entities, some of them are not initialized. If
they are not initialized imho there is no possibility that they could have been changed so
that constraints might be broken. Although hibernate validator goes for them and I get
LazyLoadingExceptions.
Also this is a change to previous versions. Has that been done on purpose?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira