Home/ Questions/Q 384191
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T15:21:23+00:00

I’m running into a strange problem using the Toplink implementation of JPA. I’m writing

  • 0

I’m running into a strange problem using the Toplink implementation of JPA. I’m writing a stand-alone application to manage loans.

I define a LOAN class that has a OneToMany (bi-directional) relationship with a NOTICE class. I created a GUI to display all the notices for a particular loan. In another part of my program I can send out late notices which is saved as a NOTICE. However, when I try to display all the notices for a loan, the late notice is NOT appearing. I’ve checked the database and an entry has been saved but for some reason the notice is not being pulled.

Only when I restart my application does the notice appear.

Because I’ve defined a OneToMany relationship, I, myself, am not making a “direct” query into the database – I’m letting JPA handle retrieving all the notices for me.

As a fix, I created a query to simply get all notices for a particular loan. This works. However, I thought by defining the OneToMany relationship between the two classes, this should be handled for me. It seems like something is not being refreshed properly… as if an “older” list of notices is being used instead of refreshing from the database?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    How are you ‘sending the late notice’? There needs to be a statement similar to:

    MyLoanInstance.listOfNotices.add(MyNoticeInstance);

    even if you already have a 

    MyNoticeInstance.setLoan(MyLoanInstance);

    statement

    Without that call, you will have to either completely reload the instance you are working with, or restart your application.

    Eclipselink does not automatically update (until reloading everything) the collection on the M side of a 1:M relationship when you modify the 1 side, nor does it update the reference in the 1 side of the 1:M relationship if you modify the collection in the M side.

    As a side note, you should consider checking out EclipseLink, it evolved out of what was TopLink, you should be able to directly swap the EclipseLink .jar with the TopLink .jar, if only to recieve a few depreciation warnings.

    Eclipse Link

    • 0