About detached

manual

JPA Entity Fields

Explains how to define and use primary keys in JPA, including composite and embedded primary keys.... Version values cannot be preserved for detached entity objects (explained in chapter 3 ) unless either the entity ...

 
forum_thread

NullPointerException while setting a new property value

Hello, we are using ObjectDB version 2.4.4 and we are unable to resolve following NPE on enhanced entity: java.lang.NullPointerException at com.objectdb.o.ENT.beforeModifyMember(ENT.java:1099) at model.PluginMetaData.__odbSet_maxAllowedDownloads(PluginMetaData.java:1) at model.PluginMetaData.setMaxAllowedDownloads(PluginMetaData.java:268) at model.PluginMetaData.setPluginDescriptor(PluginMetaData.java:94) PluginMetaData looks like this (nothing extraordinary, no relationship to other @entities): #1 2012-10-22 22:34 Hello, we are using ObjectDB version 2.4.4 and we are unable to resolve following NPE on enhanced entity: ...

 
forum_thread

Merge Issue: Attempt to reuse an existing primary key value

Hello, I have just updated my objectdb version from 2.4.6 to 2.5.5. I observed a new bug or a feature on an ordinary merge operation. This is the test case ( work in 2.4.6 version ) : 2 parents object share the same child on a ManyToMany relationship with Cascade.ALL constraint. ... It may be better to use merge only to attach detached objects, and without mixing already managed objects. ...

 
forum_thread

Mismatch client-server protocol prefix

Hello! We migrated one of our legacy webservices to Spring Boot/Spring MVC. Now i have a strange problem. At first the app runs perfectly for a couple of hours. After that it stops working and I get the following exception: #1 2015-06-17 16:02 Hello! We migrated one of our legacy webservices to Spring Boot/Spring MVC. Now i have a strange prob ...

 
forum_thread

Mapped (Inverse) LAZY @OneToMany vs. Unmapped LAZY @OneToMany

In the code example below (also attached) I would like to understand why I am able to print to console a lazy @OneToMany mapped field after a finding entity manager closes. There is a switch DO_VIEW_BEFORE_CLOSE, and when it is true the fields are accessed and output before the finding entity manager closes and as expected both a mapped @OneToMany list and an unmapped @OneToMany list are viewable: a.listA_mapped:[{A}[4]"ownedElement1", {A}[5]"ownedElement2"] a.listB_unmapped:[{B}[2]"b1", {B}[3]"b2"] #1 2012-03-14 01:37 In the code example below (also attached) I would like to understand why I am able to print to console a lazy @On ...

 
forum_thread

Failed to write the value of field using reflection (error 363) on LAZY fetch

Hi There I am using ObjectDB 2.6.3. I get the following Exception when I try to read my entities with a query where I have set to use LAZY initalization. It fails when it tries to set a 1:n member (e.g. a Modell has several Artikels) . When I remove the LAZY hint on the query execution it works. Any hints why this can happen? The Mapping of class Modell and its member: ... in a way that JPA managed entities will not be detached on exiting a method, please check Spring Framework documentation ...