From dev-return-16230-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Fri Apr 16 20:04:46 2010 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 91922 invoked from network); 16 Apr 2010 20:04:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Apr 2010 20:04:46 -0000 Received: (qmail 35557 invoked by uid 500); 16 Apr 2010 20:04:46 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 35532 invoked by uid 500); 16 Apr 2010 20:04:46 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 35524 invoked by uid 99); 16 Apr 2010 20:04:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 20:04:46 +0000 X-ASF-Spam-Status: No, hits=-1302.1 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 20:04:45 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3GK4Ow1007026 for ; Fri, 16 Apr 2010 16:04:25 -0400 (EDT) Message-ID: <16829342.16591271448264536.JavaMail.jira@thor> Date: Fri, 16 Apr 2010 16:04:24 -0400 (EDT) From: "Michael Dick (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Created: (OPENJPA-1633) Provide more information when refreshing an Entity which has been deleted. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Provide more information when refreshing an Entity which has been deleted. --------------------------------------------------------------------------- Key: OPENJPA-1633 URL: https://issues.apache.org/jira/browse/OPENJPA-1633 Project: OpenJPA Issue Type: Bug Components: jpa Reporter: Michael Dick Priority: Minor This issue was originally raised on the user's mailing list at http://n2.nabble.com/EntityNotFoundException-caused-by-EntityManager-refresh-td4901557.html#a4901557. If you have a toMany relationship and are cascading the REFRESH operation an EntityNotFondException may occur if any of the rows on the toMany side have been deleted. Finding which rows didn't exist is a bit tricky. You'll need go through two sets of nested exceptions to get to the rows that were deleted, and then you only get the primary keys, not the table / entity name. We should add the table name / entity name to the message if possible and promote them to the higher level exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira