Quantcast

[jira] [Created] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Created] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
Merge of a new object does not handle Entity Id field
-----------------------------------------------------

                 Key: OPENJPA-2142
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
             Project: OpenJPA
          Issue Type: Bug
    Affects Versions: 2.3.0, 2.2.1
            Reporter: Dianne Richards
            Assignee: Dianne Richards
             Fix For: 2.3.0, 2.2.1


When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:

<openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
FailedObject: hat.entities.Child@38d138d1
        at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
        at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
        at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
        at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
        at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
        at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
        at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
        at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
        at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
        at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
        at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
        at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
        at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
        at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
        ...

During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Work started] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on OPENJPA-2142 started by Dianne Richards.

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Closed] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dianne Richards closed OPENJPA-2142.
------------------------------------

   

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Resolved] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dianne Richards resolved OPENJPA-2142.
--------------------------------------

    Resolution: Fixed
   

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Reopened] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dianne Richards reopened OPENJPA-2142:
--------------------------------------


Reopen to commit changes for earlier releases
               

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Commented] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261696#comment-13261696 ]

Dianne Richards commented on OPENJPA-2142:
------------------------------------------

In 2.0.x there is a 2nd problem in this merge scenario. BrokerImpl.getObjectId() returns null when the StateManager in the pc object is null. This is fixed in subsequent releases by calling ApplicationIds.create(). This fix will be backported to 2.0.x in this JIRA to complete the merge fix.
               

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Commented] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261702#comment-13261702 ]

Rick Curtis commented on OPENJPA-2142:
--------------------------------------

Can you also port the testcases from trunk to 2.2.x ?

Thanks,
Rick
               

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Resolved] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dianne Richards resolved OPENJPA-2142.
--------------------------------------

    Resolution: Fixed
   

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Closed] (OPENJPA-2142) Merge of a new object does not handle Entity Id field

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/OPENJPA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dianne Richards closed OPENJPA-2142.
------------------------------------

   

> Merge of a new object does not handle Entity Id field
> -----------------------------------------------------
>
>                 Key: OPENJPA-2142
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2142
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.3.0, 2.2.1
>
>
> When a merge is done on a new object with an Id that contains an Entity, the following exception occurs:
> <openjpa-2.2.1-SNAPSHOT-r422266:1292578 nonfatal user error> org.apache.openjpa.persistence.InvalidStateException: Attempt to change a primary key field of an instance that already has a final object id.  Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.
> FailedObject: hat.entities.Child@38d138d1
> at org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyChange(StateManagerImpl.java:2108)
> at org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2043)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:236)
> at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:155)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> at org.apache.openjpa.kernel.AttachStrategy.attachCollection(AttachStrategy.java:370)
> at org.apache.openjpa.kernel.AttachStrategy.replaceList(AttachStrategy.java:431)
> at org.apache.openjpa.kernel.AttachStrategy.attachField(AttachStrategy.java:255)
> at org.apache.openjpa.kernel.AttachManager.handleCascade(AttachManager.java:267)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:241)
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3474)
> at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1214)
> at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:878)
> ...
> During the merge, a copy is made of the original object, with a copy of the key fields. But, if a key field is an Entity, it is not copied, causing this exception in later processing. The fix is to attach this field immediately after the original object is copied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Loading...