Eclipse Community Forums: EclipseLink » Behaviour merge() of detached objects

Home » Eclipse Projects » EclipseLink » Behaviour merge() of detached objects(Behaviour merge() of detached objects)

Behaviour merge() of detached objects [message #1079837]

Mon, 05 August 2013 02:21

Eclipse User

Hi,

a short EclipseLink newbie question.

We compared hibernate and EclipseLink regarding the merge of detached objects.
Hibernate return's a new java reference when we do this? When we think about a FatClient like RCP not a good behaviour...e.g. binding and etc. is a pattern not working like this.

What's the behaviour of EclipseLink? Is this a standard behaviour of the JPA2 spec?
(That's one key requirement to use EclipseLink instead of Hibernate.)

best regards
JK

[Updated on: Mon, 05 August 2013 03:01] by Moderator

Re: Behaviour merge() of detached objects [message #1082407 is a reply to message #1079837]

Thu, 08 August 2013 10:26

Eclipse User

The JPA specification requires that merge() returns the managed version of the detached object (it must be a new reference).

That is the whole point of merge(). If you don't want this, if the object is new, then consider using persist().

Previous Topic:	org.osgi.framework.BundleException: Bundle org.eclipse.persistence.jpa cannot be resolved
Next Topic:	Problem with table generation using a converter and column length

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 19:23:14 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter