Why Lazy Fetching is not working JPA

Question

i have a hard time understanding the lazy fetching since i does not work for as i read about it in a book, they say that in lazy fetching jpa will load the entities only when they are accessed through geters so i created an Arquillian project to test this concept but it does not work. here are my two entities

Person

package com.actionbazaar.model;

@Entity
@TableGenerator(
        initialValue = 5,
        name = "PERSON_SEQ",
        table = "PERSON_SEQ_TABLE",
        pkColumnName = "SEQ_NAME",
        pkColumnValue = "PERSON",
        valueColumnName = "SEQ_VALUE")
public class Person implements Serializable {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private int id;

    private String fname;
    private String lname;
    @OneToMany(fetch = FetchType.LAZY, mappedBy = "owner", cascade = CascadeType.PERSIST)
    List<Address> addresses;
    //getters and setters 
}

Address

    @Entity
public class Address implements Serializable {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private int id;
    private String city;
    private String zip;
    private String street;

    @ManyToOne
    private Person owner;
//getters and setters
}

I have a stateless session bean with this method

    public Person getFirstPerson() {
    Person p = em.find(Person.class, 1);
    em.detach(p);
    //why this call does not create an exception
    p.getAddresses().get(0);
    return p;
}

since i detached the entity before accessing the address the addresses list should be empty and when i hace detached it so it is no longer managed by the entitymanager so i should not get addresses for the person the problem is that i can fetch the addresses of that person even i have lazy fetch for addresses field and detached the entity before accessinbg the addresses field!!!! pleas some have the explanation .

An other test

Person p= myStatlessSessionBean.getFirstPerson();
myOtherStalessSesionBean.moveAllPeopleToCity("NY");
if(p.getAddresses().get(0).getCity().equals("NY"))
{
  system.out.prinln("person moved");
}
else {
system.out.prinln("person did not move");
} //prompts person did not move

Tahir Hussain Mir · Accepted Answer · 2017-02-20T05:08:04.593

5

Yeah buddy, you were right. You are not doing anything wrong here. I just opened the Pro JPA 2, 2nd edition Book and found this :

You are using glassfish-embedded which is actually causing the problem. Your code have no problem. As mentioned by the author of the above mentioned book,

Some vendors might attempt to resolve the relationship, while others might simply throw an exception or leave the attribute uninitialized.

So, in your case, the relationship is resolved rather than lazy loading. Just Implement the same example using other vendor and you will not face any problem. Here using glassfish-embedded, lazyfetch is not working. Otherwise the exception should be thrown, as the variable p is detached.

Here is the link where i also read this beautiful piece of information

Here is the snapshot from above link

edited Feb 20 '17 at 05:08

answered Feb 19 '17 at 15:21

Tahir Hussain Mir

2,506
2
19
26

yup.. You are right.. I was curious to know why this thing happened. More information gained. Thanks @achabahe – Tahir Hussain Mir Feb 19 '17 at 15:29
1

@achabahe I suspected that was the reason, but you tagged your question with "hibernate", although it seems you're not using it. That's misleading. – JB Nizet Feb 19 '17 at 15:34
may be he was trying to reach hibernate knowing people :D ? @JBNizet ^_^ – Tahir Hussain Mir Feb 19 '17 at 15:36

score 1 · Answer 2 · answered Feb 19 '17 at 15:14

1

You are only detaching the parent entity, Person. You are not detaching the children entities, Addresses, and when you get addresses, it refers to entities which are still managed by the persistence context.

If you want the children to be detached as well, you should use CascadeType.DETACH.

You might say, "But my FetchType is set to LAZY!". Just because it's LAZY, doesn't mean the object is null. Hibernate returns Proxy objects for collection types, and once you try to access them, it will populate their values.

answered Feb 19 '17 at 15:14

raminr

784
3
12

how about the second test !, i have changed the cascade to add CascadeType.DETACH, but still same problem, first i want to know if understood correctly the concept and the behavior that i am expecting is the right one – achabahe Feb 19 '17 at 15:20
1

I agree with @Tahir. Per JPA Specification: "When interoperability across vendors is required, the application must not use lazy loading." The JPA Spec also mentions that LAZY fetch is simply a hint, and that tells me that its implementation is left to the vendor. – raminr Feb 19 '17 at 15:38

Why Lazy Fetching is not working JPA

2 Answers2