Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 19716 invoked from network); 6 May 2009 23:49:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 May 2009 23:49:24 -0000 Received: (qmail 99795 invoked by uid 500); 6 May 2009 23:49:23 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 99730 invoked by uid 500); 6 May 2009 23:49:23 -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 99720 invoked by uid 99); 6 May 2009 23:49:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2009 23:49:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists+1214986235816-210739@n2.nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2009 23:49:14 +0000 Received: from tervel.nabble.com ([192.168.236.150]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M1qr8-0005ST-DM for dev@openjpa.apache.org; Wed, 06 May 2009 16:48:54 -0700 Message-ID: <1241653734403-2825223.post@n2.nabble.com> Date: Wed, 6 May 2009 16:48:54 -0700 (PDT) From: sdroscher To: dev@openjpa.apache.org Subject: OPENJPA-944 proposed fix MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: simon.droscher@elasticpath.com X-Virus-Checked: Checked by ClamAV on apache.org Hi. One of my colleagues reported an issue with loading recursion for complex relationships in issue OPENJPA-944, and then proceeded to attach a patch (and test) that solves the issue. Just wondering if any official OpenJPA developers (or anyone else on this list) would care to take a look at the solution and provide feedback, we're hoping this fix will make it into the next release of OpenJPA :) Thanks. -- View this message in context: http://n2.nabble.com/OPENJPA-944-proposed-fix-tp2825223p2825223.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.