openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Logemann (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2519) fetchType.lazy and persisting one-to-one relations
Date Thu, 24 Jul 2014 14:42:39 GMT


Marc Logemann commented on OPENJPA-2519:


i use DAO layer to get entities to my service layer. Transaction ends in DAO layer and so
i get a detached instance. The one-to-one relationsship is filled in DB but "null" in current
context because it was not loaded (lazy). Now i attach a different object to the 1:1 relation
and try to persist it. Persist means, i have this in my DAO:

 public void saveMetaData(Object metaData) {
        OpenJPAEntityManager oem = OpenJPAPersistence.cast(em);
        if (oem.isDetached(metaData)) {
        } else {

persistence.xml looks like this (i am using spring, so i dont mention entities there)

<persistence xmlns=""
    <persistence-unit name="punit">
            <property name="openjpa.Log" value="log4j"/>
            <property name="openjpa.jdbc.DBDictionary" value="mysql"/>
            <property name="openjpa.ConnectionProperties"

> fetchType.lazy and persisting one-to-one relations
> --------------------------------------------------
>                 Key: OPENJPA-2519
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 2.2.0
>            Reporter: Marc Logemann
> Hi,
> i have an entity which has a mapped superclass. In that superclass i have a 1:1 relation
which is marked "lazy". 
> Now when i load that entity, attach an object to that relation and persist it, the change
is not reflected in the database. But the jpaversion is increased. Also all other "normal"
mapped fields are persisted but not the Lazy 1:1. Of course i checked the object right before
persist and it looks pretty perfect. 
> If i remove the lazy attribute from the annotation. Everything works like expected. When
looking at OPENJPA-2505 and this issue, i am really concerned about your FetchType implementation.
This definitely feels buggy.
> And to make things more weird: On my MySQL box, the bug is non-existant. As soon as i
deploy the application (really the very same application) to MariaDB, its there.

This message was sent by Atlassian JIRA

View raw message