CODEWITHSUNDEEP
javahibernatejpapersistence
Alex Ntousias
Alex Ntousias

Reputation: 9132

How solve javax.persistence.EntityNotFoundException with JPA (not by using @NotFound)

We are using JPA to load some stuff from a database. Some entities may have optional relationships between them, e.g.

@Entity
public class First {
    ....
    @OneToOne(cascade = {CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH, CascadeType.DETACH})
    @JoinColumns(value = {
        JoinColumn(name = "A_ID", referencedColumnName = "A_ID", insertable = false, updatable = false), 
        JoinColumn(name = "B_ID", referencedColumnName = "B_ID", insertable = false, updatable = false)})
    private Second second;

When this association is present in the database, everything is working fine. When it's not, I'm getting a javax.persistence.EntityNotFoundException
What I want is instead of the exception to have this field as NULL if the association is not present.

I have tried several different things, e.g. using the optional=true in the relationship annotation (which btw is the default option), putting it as Nullable, etc. Nothing seems to do the trick, it seems like all these options are being ignored.

I found a lot of links mentioning this very same problem (and some questions here in stackoverflow) but in all of them the suggestion is to use the @NotFound annotation from Hibernate. But we do NOT want to have any dependencies to Hibernate (we want to keep everything pure JPA).

Does any of you guys know any other way to solve this?

Many thanks for all your help!

Upvotes: 21

Views: 49553

Answers (6)

Fabiano
Fabiano

Reputation: 41

Try to add the parameter optional = true to your @OneToOne annotation.

Upvotes: 2

win zaw Oo
win zaw Oo

Reputation: 1

Try to use cascade=CascadeType.ALL in @OneToMay(******).

Upvotes: -3

Dila Gurung
Dila Gurung

Reputation: 1764

It happens when you delete the associated entity id. In my case I had Product table depending upon Brand table. I deleted a row or an entity of brand id to which one of the product instance was depending upon.

Upvotes: 2

Alexandr
Alexandr

Reputation: 9505

I've met the same problem. It's not always reproducable, so I cannot test it, but here are some thoughts:

  1. The instance of your Second class is deleted, while the instance of the First class does not know anything about that.
  2. You need a way to let an instance of First know, when its instance of Second is deleted.
  3. cascade option for removing does not help here.
  4. You may try to use bidirectional relationship, when instance of First exists inside instance of Second. It let you update instance of First via instance of Second before removing second
  5. Bidirectional relationship - is evil. I would suppose in your case, that First - is owner of Second. Don't allow any service delete your Second instance directly. Let service which works with instances of First remove instance of Second. In this case you may make the "second" field nullable first, than remove instance of Second via EntityManager.
  6. You may get exception when execute queries and the 2nd level cache is enabled and query has a hint, which allows to cache its result. I would offer you get result of queries via the following method:
private List<?> getQueryResult(final Query query)
{
    try
    {
        return query.getResultList();
    }
    catch (EntityNotFoundException e)
    {
        return query.setHint("javax.persistence.cache.storeMode", CacheStoreMode.REFRESH).getResultList();
    }
}
  1. If you work with entities via EntityManger, but not via queries, and you get exception because entity is cached, you may invalidate all entities of First in cache when you delete Second.

I'd like to discuss this solution, as I cannot test it and cannot make sute it works. If somebody tries, please let me know.

PS: if somebody has a unit test for hibernate, that reproduces this issue, could you please let me know. I wish to investigate it further.

Upvotes: 2

Bj&#246;rn
Bj&#246;rn

Reputation: 1601

Below is an alternative solution for this problem. I had to build on top of an old database where the relations sometimes were corrupt. This is how I solved it by only using JPA. 

@PostLoad
public void postLoad(){
    try {
        if(getObject() != null && getObject().getId() == 0){
            setObject(null);
        }
    }
    catch (EntityNotFoundException e){
        setObject(null);
    }
}

Upvotes: 7

Adrian
Adrian

Reputation: 11

What about adding a test in the correspondent entity class:

public boolean getHasSecond() {
    if (this.Second != null) {
        return true;
    } else {
        return false;
    }
}

Like this, you can check if the relation exists...

Upvotes: 0

Related Questions