EntityManager find for primary key lookup not throwing Entit

[andrigtmiller]

In an EJB3 application that I am writing, I tried using the EntityManager's built in find method, to find a bean by its' primary key. When the bean isn't there, I want to insert a new one, and if it is there I want to update it. The problem is that the find method never throws the EntityNotFound exception, so I cannot do the insert if its not there. If I use a createQuery method, and specify the query, I get the EntityNotFound exception thrown appropriately, and my logic works perfectly.

Looking at the interface definition from Sun, it appears that the find method should throw the EntityNotFound exception from the find method. I think this is a bug, but I didn't want to add it to JIRA until someone could confirm this.

Thanks.

[bill.burke]

Known bug, I have scheduled this for Oct 6 release. It throws a hibernate specific exception correct?

[bill.burke]

Sorry, here it is in jira;

http://jira.jboss.com/jira/browse/EJBTHREE-297

[bill.burke]

FYI, call a property on the returned entity and it will throw Hibernate specific ObjectNotFound.

[bill.burke]

Also, just call find() instead and test for null.

[bill.burke]

Jeez, sorry,

getReference() should throw EntityNotFound, but it doesn't

find() returns null.

[andrigtmiller]

Thanks, I thought it probably was a bug. Good to see its already on the schedule to be fixed. For now, I can continue with the createQuery stuff, and I'll change it after the October 6th release.

[bill.burke]

Ok, yet another message :)

getReference *MAY* throw, ENFE, or, it may throw ENFE immediately after a property is accessed.

Javadoc:

If the requested instance does not exist in the database,
 * throws EntityNotFoundException when get is called or
 * when the instance state is first accessed.

In other words, use find and throw your own ENFE if the method does not exist.