How to implement lazy loading using Spring data JPA (JPARepository)?

Question

I am using Spring Data JPA and Hibernate as a provider. I've created several Repository classes which extends to JPARepository<Entity,Serializable> class. I am failing at the moment when I am fetching one entity it brings attached / connected entities along with it ! which are either connected via @OneToOne @OneToMany etc. How can I avoid fetching those connected entities ?
I have tried with @OneToMany(fetch=FetchType.LAZY) etc but still no luck. Following are my java code:
Repository

public interface TicketRepository extends JpaRepository<Ticket, Integer>{

}

Ticket Entity

@Entity
@Table(name = "tbl_tickets")
public class Ticket {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Column(name = "id")
    private Integer id;

    @Column(name = "customer", nullable = false, length = 256)
    private String customer;


    @OneToOne(cascade=CascadeType.ALL,fetch=FetchType.LAZY)
    @JoinColumn
    private User creator; 

    // ... other properties
}

Service

@Service
public class TicketService {

  public Ticket save(Ticket obj,String id) {
       User user = userService.findById(Integer.valueOf(id));
       obj.setCreator(user);
       Ticket savedTicket = ticketRepository.save(obj);
   }
}

savedTicket always fetches User entity as well which I do not want to. How could I achieve this ?
enter image description here

Thanks

Your code is fetching an user object and setting "creator" on ticket and you expect creator to be null?? — user180100
– user180100, Commented Jan 4, 2015 at 11:40
@RC. you are right, because of mapping I have to set it like that ! may be the way I mapped is wrong ! any idea on mapping part ? — Aman
– Aman, Commented Jan 4, 2015 at 11:48
there are problems with lazy fetching of OneToOne (perhaps solved in the answer of Harshal Patil below), however you should have no problems with lazy fetching of OneToMany(fetch=FetchType.LAZY). If the field gets initialized with such annotation, this might mean you access the property annotated with @OneToMany (which should be a set or a list etc.) somewhere before that. — John Donn
– John Donn, Commented Jan 5, 2015 at 8:42

Harshal Patil · Accepted Answer · 2015-01-04 16:47:42Z

1

Get Lazy loading working on nullable one-to-one mapping you need to let hibernate do Compile time instrumentation and add a @LazyToOne(value = LazyToOneOption.NO_PROXY) to the one-to-one relation.

@OneToOne(cascade=CascadeType.ALL,fetch=FetchType.LAZY)
@JoinColumn
@LazyToOne(value = LazyToOneOption.NO_PROXY)
private User creator;

Hope this will work.

answered Jan 4, 2015 at 16:47

Harshal Patil

6,7698 gold badges44 silver badges58 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Aman Over a year ago

Sorry, for late reply, I added changes suggested by you, but it says could not initialize proxy - no Session

Harshal Patil Over a year ago

@agpt Add Transactional annotation over method where your are retrieving creator.

Collectives™ on Stack Overflow

How to implement lazy loading using Spring data JPA (JPARepository)?

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related