Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <47FA0EDE.10902@cyberspaceroad.org>
Date: Mon, 07 Apr 2008 13:09:02 +0100
From: Adam Hardy <adam.sql@cyberspaceroad.org>
User-Agent: Icedove 1.5.0.14pre (X11/20080305)
MIME-Version: 1.0
To: users@openjpa.apache.org
Subject: persisting an entity and JPA behaviour with referenced entities
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

I've got an issue with the persist operation, when I use a detached entity as 
one of the entity's referenced entities.

OpenJPA throws the
org.apache.openjpa.persistence.EntityExistsException: Attempt to persist 
detached object 
"org.apache.openjpa.enhance.org$permacode$atomictest$domain$Genus$pcsubclass@1c527be".

The situation is this: my MVC layer has received a new entity which it must 
create. The parent entity for this is found in a cache, in a detached state.

What I'd like to know, is why is JPA forcing me to merge this detached entity 
before allowing me to persist the new child?

It means I can't use the cache, or I have to program the DAO to merge all 
referenced entities. This latter option seems like a job that JPA should be 
doing. JPA knows this parent is a detached entity, so why can't it merge the 
managed entity?

I can't see any text in the EJB spec that would mandate this behaviour, yet 
Hibernate does it too.

Regards
Adam