<div>
I just tried this using the hibernate JPA implementation and it seems that this works just fine. The Department object is not loaded before the Employee is persisted.<br />
<br />
In fact it does not even throw the EntityNotFoundException if the dept does not exists, but em.persist(emp) will fail due to a constraint violation...
</div>


I just tried this using the hibernate JPA implementation and it seems that this works just fine. The Department object is not loaded before the Employee is persisted.

In fact it does not even throw the EntityNotFoundException if the dept does not exists, but em.persist(emp) will fail due to a constraint violation...

<div>
<div class="content wysiwyg-content">
Ok, I got the point, <br />
<br />
But the flush will fail on the employee since there is a NOT NULL constraint on the department id :(<br />
<br />
Have an idea?<br />
<br />

</div>
</div>


Ok, I got the point, 

But the flush will fail on the employee since there is a NOT NULL constraint on the department id :(

Have an idea?



Other Issue (See related Solution)

Java Enterprise Edition (Java EE) is a specification defining a collection of Java-based server and client technologies and how they interoperate. Java EE specifies server and client architectures and uses profiles to define technology sets targeted at specific classes of applications. All Java EE profiles share a set of common features, such as naming and resource injection, packaging rules and security requirements.