1:54 p.m.
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
2:43 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-586) Hibernate validator initializes lazy proxies
[
https://hibernate.onjira.com/browse/HV-586?page=com.atlassian.jira.plugin...
]
Hardy Ferentschik commented on HV-586:
--------------------------------------
I am not aware of any changes in this area. What exactly do you mean with loading lazy
properties? Associations? For this purpose the _TraversableResolver_ is used. If an
association has not been initialized it does not eat validated.
Can you provide a test case or at least describe your setup in more detail.
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
3:14 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-586) Hibernate validator initializes lazy proxies
[
https://hibernate.onjira.com/browse/HV-586?page=com.atlassian.jira.plugin...
]
Michael G commented on HV-586:
------------------------------
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
6:04 a.m.
New subject: [Hibernate-JIRA] Commented: (HV-586) Hibernate validator initializes lazy proxies
[
https://hibernate.onjira.com/browse/HV-586?page=com.atlassian.jira.plugin...
]
Hardy Ferentschik commented on HV-586:
--------------------------------------
I think you just found the answer to your question yourself. _@NotEmpty_ will initialize
the proxy, because it needs to check the size of the set.
One solution could be to map the collection extra lazy (Hibernate specific feature) in
which case only the size of the collection gets queried:
{code}
class A {
@OneToMany
@LazyCollection(LazyCollectionOption.EXTRA)
@Valid
@NotEmpty
private Set<B> b;
}
{code}
I think you still will need a open session though. This is something which is always
needed when working with lazy collections.
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
6:06 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HV-586) Hibernate validator initializes lazy proxies
[
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
6:06 a.m.
New subject: [Hibernate-JIRA] Resolved: (HV-586) Hibernate validator initializes lazy proxies
[
https://hibernate.onjira.com/browse/HV-586?page=com.atlassian.jira.plugin...
]
Hardy Ferentschik resolved HV-586.
----------------------------------
Resolution: Won't Fix
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
8:53 a.m.
New subject: [Hibernate-JIRA] Commented: (HV-586) Hibernate validator initializes lazy proxies
[
https://hibernate.onjira.com/browse/HV-586?page=com.atlassian.jira.plugin...
]
Michael G commented on HV-586:
------------------------------
Well, I would say if this collection is not initialized, who should have possibly broken
the constraint? So imho there is no need for checking it.
I am going with JPA, I guess there is no extra lazy available.
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
12:01 p.m.
New subject: [Hibernate-JIRA] (HV-586) Hibernate validator initializes lazy proxies
4386
days inactive
4437
days old
hibernate-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
Gunnar Morling (JIRA) -
Hardy Ferentschik (JIRA)
-
Michael G (JIRA)