Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 67223 invoked from network); 2 Dec 2010 16:42:55 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Dec 2010 16:42:55 -0000 Received: (qmail 93033 invoked by uid 500); 2 Dec 2010 16:42:55 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 92769 invoked by uid 500); 2 Dec 2010 16:42:53 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 92755 invoked by uid 99); 2 Dec 2010 16:42:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Dec 2010 16:42:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com designates 209.85.213.174 as permitted sender) Received: from [209.85.213.174] (HELO mail-yx0-f174.google.com) (209.85.213.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Dec 2010 16:42:47 +0000 Received: by yxt3 with SMTP id 3so3858118yxt.33 for ; Thu, 02 Dec 2010 08:42:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=ZJIhpsjah3NY44KIe7bLYPDdKP/xc3WbP8zwE3wFJ8I=; b=eBSvADPF9BFILFsTkGn9DYw5YxAW4lfD0nVecvMdRCtt9jOQe+kaQjHN7LkWp5Fdu7 0HPZlqA6002NLaL2Od6hTTuRFd2ApLzqvi6UPjoUO2FIslFv4TnFJiOnrtc77IoExVLl YzjE0Bz45dhMSPcR6cvUWJSwSoSJLVWL2HBSo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=KNmpn4q4Vkw3pnwiW7NraKG7nr+WiUtt5XrWkHnFHsqyJQJ25fqzwOCUFYt9JBWnWY rXryasJaNN3qNT0I4Txv5aQ01kVUor1Aoqzs7qspRfqmsFlb9+OXd/0cbupJdKqn8vS4 Mj3dYkD47RgrVzufUusI++RJaXIt56Jlcnngg= Received: by 10.90.149.17 with SMTP id w17mr1593040agd.74.1291308146922; Thu, 02 Dec 2010 08:42:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.91.128.8 with HTTP; Thu, 2 Dec 2010 08:42:05 -0800 (PST) In-Reply-To: <4CF7A803.2020906@su3analytics.com> References: <4CEFA21D.2070002@su3analytics.com> <4CF7A803.2020906@su3analytics.com> From: Michael Dick Date: Thu, 2 Dec 2010 10:42:05 -0600 Message-ID: Subject: Re: Error merging in entity - GeneratedValue To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=0016364ed6c26494540496701b85 --0016364ed6c26494540496701b85 Content-Type: text/plain; charset=ISO-8859-1 I noticed your email, but didn't get a chance to look into the problem in any depth. I think there are unit tests that cover this scenario (at least with the default options). If you have any properties set in persistence.xml, could you post them? The JIRA suggests that the problem is related to detached state - which might help to narrow down the problem. Regards, -mike On Thu, Dec 2, 2010 at 8:06 AM, Joel Halbert wrote: > Hi, > Anyone able to comment on the below? I should mention I'm using 2.0.1 > Cheers > > J > > On 26/11/10 12:03, Joel Halbert wrote: > >> Hi Folks, >> >> I'm getting the following response when trying to merge in an existing >> entity: >> >> >> org.apache.openjpa.persistence.InvalidStateException: The generated value >> processing detected an existing value assigned to this field: com.su3ana >> lytics.crawler.model.GlobalFrontier.id. This existing value was either >> provided via an initializer or by calling the setter method. You either >> need to remove the @GeneratedValue annotation or mod >> ify the code to remove the initializer processing. >> at >> org.apache.openjpa.util.ApplicationIds.assign(ApplicationIds.java:483) >> >> I can confirm that the id field is not set, either via a constructor, or >> by a setter method. >> >> Is it possible that it might be related to the followig issue in JIRA? >> >> https://issues.apache.org/jira/browse/OPENJPA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619733< >> https://issues.apache.org/jira/browse/OPENJPA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619733> >> >> >> If so, is there a fix/patch available? >> >> Cheers, >> Joel >> >> > --0016364ed6c26494540496701b85--