From dev-return-21327-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 3 19:06:00 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED62EE4BB for ; Mon, 3 Dec 2012 19:05:59 +0000 (UTC) Received: (qmail 47689 invoked by uid 500); 3 Dec 2012 19:05:59 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 46981 invoked by uid 500); 3 Dec 2012 19:05:58 -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 46595 invoked by uid 99); 3 Dec 2012 19:05:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2012 19:05:58 +0000 Date: Mon, 3 Dec 2012 19:05:58 +0000 (UTC) From: "Heath Thomann (JIRA)" To: dev@openjpa.apache.org Message-ID: <1182669643.54511.1354561558622.JavaMail.jiratomcat@arcas> In-Reply-To: <573802510.28806.1351192152685.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (OPENJPA-2284) NPE occurs when is added to a in an orm. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Heath Thomann updated OPENJPA-2284: ----------------------------------- Attachment: OPENJPA-2284-mvn-test.zip I'm attaching my test to recreate this issue. This is a stand alone maven test/project which can be imported into eclipse as an existing mvn project.....sorry, have not have time to convert it to a test which can be applied to OpenJPA.....the 'Simple.java' entity and orm.xml are the two pertinent pieces..... Thanks, Heath > NPE occurs when is added to a in an orm. > --------------------------------------------------------------------------------------- > > Key: OPENJPA-2284 > URL: https://issues.apache.org/jira/browse/OPENJPA-2284 > Project: OpenJPA > Issue Type: Bug > Components: jpa > Affects Versions: 2.0.3, 2.3.0, 2.2.1 > Reporter: Heath Thomann > Assignee: Heath Thomann > Priority: Minor > Attachments: OPENJPA-2284-mvn-test.zip > > > Take this entity: > public class Simple { > private int id; > private String name; > Take this orm.xml entry: > > > MySchema > > > > > > > > > > > > With this, the following exception will occur: > Caused by: org.xml.sax.SAXException: file:/E:/jpa/openJPAcode/PMR93141/target/test-classes/META-INF/orm.xml [Location: Line: 16, C: 23]: An error was encountered while parsing element "id". Make sure the metadata file is correctly formatted. [java.lang.NullPointerException] > at org.apache.openjpa.lib.meta.XMLMetaDataParser.getException(XMLMetaDataParser.java:739) > at org.apache.openjpa.lib.meta.CFMetaDataParser.endElement(CFMetaDataParser.java:147) > at org.apache.openjpa.lib.meta.XMLMetaDataParser.endElement(XMLMetaDataParser.java:499) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:579) > at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:218) > at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:873) > at org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:590) > at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(XMLDTDValidator.java:777) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:748) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1453) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333) > at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524) > at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580) > at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152) > at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) > at org.apache.openjpa.lib.meta.XMLMetaDataParser.parseNewResource(XMLMetaDataParser.java:421) > ... 60 more > If I comment out the '' entry, all works fine. Note that in the above XML I've added the and entries as well. Neither of these have an effect on the outcome (they could simply be removed). I was thinking that if the issue occurred for the cascade stanza that it might also occur for the entry since the two are similar in their XML definition (XSD). However, this issue seems isolated to just the cascade stanza. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21328-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 4 09:50:26 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E44BCE4FD for ; Tue, 4 Dec 2012 09:50:25 +0000 (UTC) Received: (qmail 76424 invoked by uid 500); 4 Dec 2012 09:50:25 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 76119 invoked by uid 500); 4 Dec 2012 09:50:20 -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 76043 invoked by uid 99); 4 Dec 2012 09:50:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 09:50:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fabio.martelli@gmail.com designates 74.125.83.46 as permitted sender) Received: from [74.125.83.46] (HELO mail-ee0-f46.google.com) (74.125.83.46) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 09:50:07 +0000 Received: by mail-ee0-f46.google.com with SMTP id e53so2415498eek.33 for ; Tue, 04 Dec 2012 01:49:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=+OfJelzd5GYJLOzvZWwfEZ/EQ9qSHUPTLSx1m4fWE9M=; b=i0do1L5NYl7N7qk7K9uyLH9idriGInAFHK9zijPbFmZ1bGdvjNNC+QbsABKod9DsxW Op16vcH+4nhKyO8JOBHPIsm4NThxX+iSCNou4clJfYwvQGO0H8jzioq2GaBS2VPls7at UogZeaBxte+aDmwcXvLAdm5eZQgX9cq4TR5bShm0iPcyftAP9gLeQImULW5O2PZbKLbA 93vC6cG/inU9Gq0C1nLGcrSEZfmhii6UduoX4Y07kFoM6fSVfMerBWqZJT1POvwNeLZV ZkCBYLT21p1UHdinLqXOBW/6gRyOiAfefvC+7+THRxtApVXWmU6zr4DzVgxowgRgrkD8 JgCQ== Received: by 10.14.219.72 with SMTP id l48mr8185857eep.37.1354614587627; Tue, 04 Dec 2012 01:49:47 -0800 (PST) Received: from macpro.pluto.org (rovere.tirasa.net. [78.134.5.44]) by mx.google.com with ESMTPS id f49sm1590039eep.12.2012.12.04.01.49.45 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 04 Dec 2012 01:49:46 -0800 (PST) From: Fabio Martelli Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: NullPointerException into JDBCStoreQuery Date: Tue, 4 Dec 2012 10:49:44 +0100 Message-Id: To: dev@openjpa.apache.org Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) X-Virus-Checked: Checked by ClamAV on apache.org Hi All, I'm working on a customization around slice (openjpa version = 2.3.0-SNAPSHOT). Checking two subsequent bulk deletes about the same object a = NullPointerException will be raised. The exception has been retrieved at JDBCStoreQuery, row 527. Considering that, in case of serialization, the LifecycleEventManager = can be null, is the attached patch acceptable/applicable? Please let me know what you think about. Best regards, F. --- = openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/JDBCStoreQuery.j= ava (revision 1415215) +++ = openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/JDBCStoreQuery.j= ava (working copy) @@ -524,7 +524,7 @@ // execute in-memory so the callbacks are invoked LifecycleEventManager mgr =3D = ctx.getStoreContext().getBroker() .getLifecycleEventManager(); - if (mgr.hasDeleteListeners(null, mappings[i])) + if (mgr!=3Dnull && mgr.hasDeleteListeners(null, = mappings[i])) return null; } } From dev-return-21329-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 4 15:51:05 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2DFA7E331 for ; Tue, 4 Dec 2012 15:51:05 +0000 (UTC) Received: (qmail 33607 invoked by uid 500); 4 Dec 2012 15:51:05 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 33192 invoked by uid 500); 4 Dec 2012 15:50:57 -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 33124 invoked by uid 99); 4 Dec 2012 15:50:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 15:50:55 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of allee8285@gmail.com designates 209.85.223.174 as permitted sender) Received: from [209.85.223.174] (HELO mail-ie0-f174.google.com) (209.85.223.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 15:50:47 +0000 Received: by mail-ie0-f174.google.com with SMTP id c11so7094826ieb.33 for ; Tue, 04 Dec 2012 07:50:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Ot4oN7RdYfg1o/ZQ5koT00bO1VPSASVUQ8g8OAe/cmk=; b=Ep+NtDp5oC2Nyngwj/pzpYl+aTGdCaosTEZmcOQ/EMMbVRYs2JFe3ocHR20t6YuGoH vSpvMkU+Kef7oAWAPCgPPG/so/fXoaM9SrKB3MXWRrpGrBQVNvJEUNYzHc65mEJsmI8H De0Ke6knpU4qx6bB7Y5xtVrKb2c/eplcpC0CxliIrSo2zb7OT5q0Ae2d0ofMY+byoShg 84qIzU9zeBzm60MXl3XDwTg7wN2ggO1to/tWqokjl+590Qv3EwpO/+zdev7Fyg6F/rgs XPlsP7+k4CohE/bnWuqWK3QUbpA10U9WoGBSrnpCyhqgJtWDjuiG5IXmeiqDYxXBnkNS svGg== MIME-Version: 1.0 Received: by 10.50.203.74 with SMTP id ko10mr3182848igc.26.1354636226386; Tue, 04 Dec 2012 07:50:26 -0800 (PST) Received: by 10.50.73.73 with HTTP; Tue, 4 Dec 2012 07:50:26 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Dec 2012 09:50:26 -0600 Message-ID: Subject: Re: NullPointerException into JDBCStoreQuery From: Albert Lee To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=14dae934078712dbd304d008d3d9 X-Virus-Checked: Checked by ClamAV on apache.org --14dae934078712dbd304d008d3d9 Content-Type: text/plain; charset=ISO-8859-1 You may want to open a JIRA and attach a patch to it. Albert Lee. On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli wrote: > Hi All, > I'm working on a customization around slice (openjpa version > 2.3.0-SNAPSHOT). > Checking two subsequent bulk deletes about the same object a > NullPointerException will be raised. > > The exception has been retrieved at JDBCStoreQuery, row 527. > Considering that, in case of serialization, the LifecycleEventManager can > be null, is the attached patch acceptable/applicable? > > Please let me know what you think about. > > Best regards, > F. > > --- > openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/JDBCStoreQuery.java > (revision 1415215) > +++ > openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/JDBCStoreQuery.java > (working copy) > @@ -524,7 +524,7 @@ > // execute in-memory so the callbacks are invoked > LifecycleEventManager mgr = > ctx.getStoreContext().getBroker() > .getLifecycleEventManager(); > - if (mgr.hasDeleteListeners(null, mappings[i])) > + if (mgr!=null && mgr.hasDeleteListeners(null, > mappings[i])) > return null; > } > } > > > > > -- Albert Lee. --14dae934078712dbd304d008d3d9-- From dev-return-21330-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 4 16:05:47 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 430FCE3C7 for ; Tue, 4 Dec 2012 16:05:47 +0000 (UTC) Received: (qmail 75862 invoked by uid 500); 4 Dec 2012 16:05:47 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 75677 invoked by uid 500); 4 Dec 2012 16:05: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 75650 invoked by uid 99); 4 Dec 2012 16:05:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 16:05:45 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of curtisr7@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 16:05:39 +0000 Received: by mail-la0-f46.google.com with SMTP id p5so3707391lag.33 for ; Tue, 04 Dec 2012 08:05:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=q2HVEP+mKvG1y4Sf6lrjkhQ3EqBXS0ieMoopzNjg/Xw=; b=JRPH6VXkBiO5lv8JZ6cK7+4iXNH/10p/WQfSuVYHVNgTrv9tcb1v/XXBjhH8EOnCev 1Y7HFt1UqW/MvPy4tGQ2M7WovKrMG1pTR5EPz8v3XYVwVi0JiTBsvNbbWGFnPnD7LFPF fbxLRFToCr4O7IKK5BsLiz5Qog7MYsKKUbhxrOZCwJHDNk9YW9/yX7zhrgj/DjXoZGPR W3BUWnk/ELc96X7uqRBPCuKDAgpb+TKHMjcP4EnUtEBzOe4WYmnduYjZMnXti6zpl6vh h0qn1EPdfJPyXyovorzkR7sUIWuSDe7UJBuK5PE1Dlv8A/mdQeS9FJESXzNd9QeuUW9v 6sQQ== MIME-Version: 1.0 Received: by 10.152.105.33 with SMTP id gj1mr13540903lab.49.1354637117775; Tue, 04 Dec 2012 08:05:17 -0800 (PST) Received: by 10.114.13.199 with HTTP; Tue, 4 Dec 2012 08:05:17 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Dec 2012 10:05:17 -0600 Message-ID: Subject: Re: NullPointerException into JDBCStoreQuery From: Rick Curtis To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=f46d040716e3345ec904d00908bd X-Virus-Checked: Checked by ClamAV on apache.org --f46d040716e3345ec904d00908bd Content-Type: text/plain; charset=ISO-8859-1 I'm not certain the null check is the correct change.... Why aren't we getting a LifeCycleEventManager on deserialization? Thanks, Rick On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli wrote: > JDBCStoreQuery -- *Rick Curtis* --f46d040716e3345ec904d00908bd-- From dev-return-21331-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 4 16:30:52 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9A16D3DA for ; Tue, 4 Dec 2012 16:30:52 +0000 (UTC) Received: (qmail 59996 invoked by uid 500); 4 Dec 2012 16:30:52 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 59818 invoked by uid 500); 4 Dec 2012 16:30:52 -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 59797 invoked by uid 99); 4 Dec 2012 16:30:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 16:30:51 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fabio.martelli@gmail.com designates 209.85.215.174 as permitted sender) Received: from [209.85.215.174] (HELO mail-ea0-f174.google.com) (209.85.215.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 16:30:42 +0000 Received: by mail-ea0-f174.google.com with SMTP id e13so1883588eaa.33 for ; Tue, 04 Dec 2012 08:30:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=Kz2WxzE2sqFBOiyO8eIwW1R5rhK+p63etQlYp8yL9Ig=; b=HEuFub3Us2ghII0cDwFmGLCNT0f7ZDTK5ouAYKs8irm4xCpaHX56HKuRvnZf7HRp8V /6Ott0vWAjpwBtQpFDGVPUPvpOu6prEvguxVHo6nck/C9bkMF+1VLSph2wRTciYecyB/ AwCEfid/MPM0b6cO3YBqh0t8knGV1lLFg+NHJVbqE2lsX0zPRSakHLqqbMsgNz2jxSUj zJUMZAUHcg0O9sEQ0YP+2GsiBMmPAUmWBH/EoUH5LT4Sz3Vm6vyDmM6yrlkDbjV5Odz9 L4uHL9+YMFaByoYkeIqyPgPLwYRsVMUz4q/7ECnAqlDIyWsoVmwwSq+QxD9UClkLQO3M WD4Q== Received: by 10.14.174.198 with SMTP id x46mr43553266eel.23.1354638622051; Tue, 04 Dec 2012 08:30:22 -0800 (PST) Received: from macpro.pluto.org (rovere.tirasa.net. [78.134.5.44]) by mx.google.com with ESMTPS id b2sm3450356eep.9.2012.12.04.08.30.19 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 04 Dec 2012 08:30:21 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: NullPointerException into JDBCStoreQuery From: Fabio Martelli In-Reply-To: Date: Tue, 4 Dec 2012 17:30:18 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8F7344F8-C8AE-42B6-AF4C-B684C7AD22CD@gmail.com> References: To: dev@openjpa.apache.org X-Mailer: Apple Mail (2.1085) X-Virus-Checked: Checked by ClamAV on apache.org Il giorno 04/dic/2012, alle ore 17.05, Rick Curtis ha scritto: > I'm not certain the null check is the correct change.... Why aren't we > getting a LifeCycleEventManager on deserialization? Hi Rick, BrokerImpl initialize LifecycleEventManager into the initialize method. =46rom my PPOV, the piece of code that suggest what I wrote in my email = is the following .... if (!fromDeserialization) { _lifeEventManager =3D = _conf.getLifecycleEventManagerInstance(); ..... } ..... Now, fromDeserialization is a method's parameter so someone could = provide a "true" value for it. In particular, the following chain seems to provide a "true" value for = fromDeserialization parameter BrokerImpl.readObject =97> = AbstractBrokerFactory.initializeBroker =97> BrokerImpl.initialize Please tell me if I wrong or I missed something. Best regards, F. Now, since initialize can be called by BrokerFactory.initializeBroker > Thanks, > Rick >=20 > On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli = wrote: >=20 >> JDBCStoreQuery >=20 >=20 >=20 >=20 > --=20 > *Rick Curtis* From dev-return-21332-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 5 02:49:01 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B199ED045 for ; Wed, 5 Dec 2012 02:49:01 +0000 (UTC) Received: (qmail 83339 invoked by uid 500); 5 Dec 2012 02:49:01 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 83304 invoked by uid 500); 5 Dec 2012 02:49:01 -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 83275 invoked by uid 99); 5 Dec 2012 02:49:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 02:49:00 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-vc0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 02:48:53 +0000 Received: by mail-vc0-f174.google.com with SMTP id d16so4469798vcd.33 for ; Tue, 04 Dec 2012 18:48:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=QtcYFDA5jnRr6gEAzkIm/hXFascPJTMjzJlJJYfNpQk=; b=ijtpHxlsZYeLNaOMFj49pvIjxOC3tYmBUiG24m4BClikAnprimqXFYnHvOegdevKr1 1WJx19FUxWXnxh42Bjw/kMMyuzwFXiwqju78LMzIalDqKKOeqkcbsFq20m7I07rgC0iK LVjBvizMct0k1GpTBoNSs7KLV4mML0LGKMjWUIiPhmRbSjrsoMGHiOkAq++wZXuLU5Xt /RDkg/6Pj8EDeqWHTxf7CPERnI4Ek+qHyiMixCpGTZSSr0Gz7bP67gFJDgJwvuy6lW8O Z7iJn6oU5H4D3NsCQ09QdfOva05vQH3+9sAMpAy2xTnwz5C/xU/VLVwajGv9TXIxzypY aUxw== Received: by 10.220.115.20 with SMTP id g20mr13706749vcq.31.1354675712855; Tue, 04 Dec 2012 18:48:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.172.9 with HTTP; Tue, 4 Dec 2012 18:48:12 -0800 (PST) In-Reply-To: <8F7344F8-C8AE-42B6-AF4C-B684C7AD22CD@gmail.com> References: <8F7344F8-C8AE-42B6-AF4C-B684C7AD22CD@gmail.com> From: Michael Dick Date: Tue, 4 Dec 2012 20:48:12 -0600 Message-ID: Subject: Re: NullPointerException into JDBCStoreQuery To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=f46d0434c2eca68f9204d0120474 X-Virus-Checked: Checked by ClamAV on apache.org --f46d0434c2eca68f9204d0120474 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It seems to me that there are two possible use cases here. 1.) The Broker has been serialized and deserialized. In this case the code expects that the LifeCycleEventManager will be serialized with the Broker and the saved LCEventManager should be used from that point on (or at least until free() is called). To investigate this case it'd be handy to serialize/deserialize the broker and see if the LCEventManager is preserved. If not then perhaps it's a bug in serialization. If it is preserved then the lack of a null check isn't (necessarily) a red flag. 2.) The LCEventManager becomes null after doing two bulk delete operations (this was mentioned in the original email). Unless the extension to slice or your testcase are serializing the broker this is a different issue. In either case I'd suggest creating a repeatable testcase, or steps to reproduce with 'vanilla' OpenJPA and opening a JIRA. -mike On Tue, Dec 4, 2012 at 10:30 AM, Fabio Martelli w= rote: > > Il giorno 04/dic/2012, alle ore 17.05, Rick Curtis ha scritto: > > > I'm not certain the null check is the correct change.... Why aren't we > > getting a LifeCycleEventManager on deserialization? > > Hi Rick, > BrokerImpl initialize LifecycleEventManager into the initialize method. > > From my PPOV, the piece of code that suggest what I wrote in my email is > the following > > .... > if (!fromDeserialization) { > _lifeEventManager =3D _conf.getLifecycleEventManagerInstance(= ); > ..... > } > ..... > > Now, fromDeserialization is a method's parameter so someone could provide > a "true" value for it. > > In particular, the following chain seems to provide a "true" value for > fromDeserialization parameter > > BrokerImpl.readObject =97> AbstractBrokerFactory.initializeBroker= =97> > BrokerImpl.initialize > > Please tell me if I wrong or I missed something. > > Best regards, > F. > > Now, since initialize can be called by BrokerFactory.initializeBroker > > > Thanks, > > Rick > > > > On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli >wrote: > > > >> JDBCStoreQuery > > > > > > > > > > -- > > *Rick Curtis* > > --f46d0434c2eca68f9204d0120474-- From dev-return-21333-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 5 08:36:48 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B5AB9E0A9 for ; Wed, 5 Dec 2012 08:36:48 +0000 (UTC) Received: (qmail 46922 invoked by uid 500); 5 Dec 2012 08:36:48 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 46606 invoked by uid 500); 5 Dec 2012 08:36:44 -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 46513 invoked by uid 99); 5 Dec 2012 08:36:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 08:36:40 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fabio.martelli@gmail.com designates 209.85.215.174 as permitted sender) Received: from [209.85.215.174] (HELO mail-ea0-f174.google.com) (209.85.215.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 08:36:30 +0000 Received: by mail-ea0-f174.google.com with SMTP id e13so2190136eaa.33 for ; Wed, 05 Dec 2012 00:36:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=FHA7IphSzPpLaXg/yEd7mZ+jZknSWCPTR1lSG679lyg=; b=rGs1I865r7C0CI397s5i/4e6gaTMO4LWGfFZgcIXE5DSFnRc1UlBXeu7kFcjn/HVFX 8zkYbq9rwsx8rXVgAEXiC5PJN9cZZHozL9xbuLVv5lNuImZl0MNgNJo3ZAQPCP7nZM05 sCO6ca53zrgdf5GSBUaGhkXyZM5id0BMplaVfBgCTiUKS+4AcacehdnNJsK6qwn778AY OejhkUiRL6Ht+pzpk9p7qVzZoUu+VDEMCSBhp2DyGsXGrhfYMHEDPeLVTd1OWbGFhInT x0RQGVG5cyQW65jD3XcwlSgrNFDSYt+N68TNFaYqwKEpaRDYHKlQZFkrYmmhhrIXQ8tt KZKg== Received: by 10.14.225.194 with SMTP id z42mr51533889eep.22.1354696570503; Wed, 05 Dec 2012 00:36:10 -0800 (PST) Received: from macpro.pluto.org (rovere.tirasa.net. [78.134.5.44]) by mx.google.com with ESMTPS id y44sm7870702eel.14.2012.12.05.00.36.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 05 Dec 2012 00:36:09 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: NullPointerException into JDBCStoreQuery From: Fabio Martelli In-Reply-To: Date: Wed, 5 Dec 2012 09:36:06 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7248D85C-47D5-49E0-B371-216CB07A752C@gmail.com> References: <8F7344F8-C8AE-42B6-AF4C-B684C7AD22CD@gmail.com> To: dev@openjpa.apache.org X-Mailer: Apple Mail (2.1085) X-Virus-Checked: Checked by ClamAV on apache.org Il giorno 05/dic/2012, alle ore 03.48, Michael Dick ha scritto: > It seems to me that there are two possible use cases here. >=20 > 1.) The Broker has been serialized and deserialized. In this case the = code > expects that the LifeCycleEventManager will be serialized with the = Broker > and the saved LCEventManager should be used from that point on (or at = least > until free() is called). >=20 > To investigate this case it'd be handy to serialize/deserialize the = broker > and see if the LCEventManager is preserved. If not then perhaps it's a = bug > in serialization. If it is preserved then the lack of a null check = isn't > (necessarily) a red flag. >=20 > 2.) The LCEventManager becomes null after doing two bulk delete = operations > (this was mentioned in the original email). Unless the extension to = slice > or your testcase are serializing the broker this is a different issue. >=20 > In either case I'd suggest creating a repeatable testcase, or steps to > reproduce with 'vanilla' OpenJPA and opening a JIRA. Hi Michael, I'm able to reproduce the problem only if I use slice. Actually, it seems that joining the QueryCompilationCache to a slice = configuration cause the problem in object. I changed the org.apache.openjpa.slice.TestBasic class in order to = reproduce the problem. Please, take a look at the diff below. --- src/test/java/org/apache/openjpa/slice/TestBasic.java = (revision 1415215) +++ src/test/java/org/apache/openjpa/slice/TestBasic.java (working = copy) @@ -46,8 +46,14 @@ =20 =20 public void setUp() throws Exception { - super.setUp(PObject.class, Person.class, Address.class, = Country.class,=20 + super.setUp("openjpa.QueryCompilationCache", "true", + PObject.class, Person.class, Address.class, Country.class,=20= CLEAR_TABLES); + EntityManager em =3D emf.createEntityManager(); + em.getTransaction().begin(); + em.createQuery("DELETE FROM PObject p").executeUpdate(); + em.getTransaction().commit(); + em.close(); } Slice should support QueryCompilationCache, shouldn't it? Please, let me know if I have to open a new issue on Jira. Best regards, F. > -mike >=20 >=20 > On Tue, Dec 4, 2012 at 10:30 AM, Fabio Martelli = wrote: >=20 >>=20 >> Il giorno 04/dic/2012, alle ore 17.05, Rick Curtis ha scritto: >>=20 >>> I'm not certain the null check is the correct change.... Why aren't = we >>> getting a LifeCycleEventManager on deserialization? >>=20 >> Hi Rick, >> BrokerImpl initialize LifecycleEventManager into the initialize = method. >>=20 >> =46rom my PPOV, the piece of code that suggest what I wrote in my = email is >> the following >>=20 >> .... >> if (!fromDeserialization) { >> _lifeEventManager =3D = _conf.getLifecycleEventManagerInstance(); >> ..... >> } >> ..... >>=20 >> Now, fromDeserialization is a method's parameter so someone could = provide >> a "true" value for it. >>=20 >> In particular, the following chain seems to provide a "true" value = for >> fromDeserialization parameter >>=20 >> BrokerImpl.readObject =97> = AbstractBrokerFactory.initializeBroker =97> >> BrokerImpl.initialize >>=20 >> Please tell me if I wrong or I missed something. >>=20 >> Best regards, >> F. >>=20 >> Now, since initialize can be called by BrokerFactory.initializeBroker >>=20 >>> Thanks, >>> Rick >>>=20 >>> On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli = >> wrote: >>>=20 >>>> JDBCStoreQuery >>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>> *Rick Curtis* >>=20 >>=20 From dev-return-21334-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 5 15:06:37 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A489DE951 for ; Wed, 5 Dec 2012 15:06:37 +0000 (UTC) Received: (qmail 85848 invoked by uid 500); 5 Dec 2012 15:06:37 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 85533 invoked by uid 500); 5 Dec 2012 15:06:31 -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 85471 invoked by uid 99); 5 Dec 2012 15:06:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 15:06:29 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com designates 209.85.212.41 as permitted sender) Received: from [209.85.212.41] (HELO mail-vb0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 15:06:22 +0000 Received: by mail-vb0-f41.google.com with SMTP id l22so5135153vbn.0 for ; Wed, 05 Dec 2012 07:06:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/JB/dmCbSVevV1vi6IZNvrXsNTKd00oD5QWlm0RPTeA=; b=gD7gzEpdv9+1JfWpc+/CkMGGbW9+uvsZZctYEbeZ+glswfE2Yaiy75hul3BwCF0GaW mGR/YnrUkiBVvSdhFTh9XraUU5R3JukjWrxw/6o58cEelEEQrvR+NYps3qu7lXH4gsAO Pst71mfj5wfiiktwXjBK6Ep4iKKNezHarOxHY5zXwuSfvtQfIwG2mfahVKZ4DjvHi4bH nlf3PYbSbQKUKBuQuYxVK2qiXcOkzC0XHJTtlJTu+YNp19jBiZEwD+9J1Z91xGNRSjuB +VixXgNpura/8ut9Ia/b0WuqEAhby2F6j8VfNbHiUDsK9lhAlu+6QXvxvgtUS66rjgdZ ZHEg== Received: by 10.52.94.108 with SMTP id db12mr13609616vdb.119.1354719961598; Wed, 05 Dec 2012 07:06:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.172.9 with HTTP; Wed, 5 Dec 2012 07:05:41 -0800 (PST) In-Reply-To: <7248D85C-47D5-49E0-B371-216CB07A752C@gmail.com> References: <8F7344F8-C8AE-42B6-AF4C-B684C7AD22CD@gmail.com> <7248D85C-47D5-49E0-B371-216CB07A752C@gmail.com> From: Michael Dick Date: Wed, 5 Dec 2012 09:05:41 -0600 Message-ID: Subject: Re: NullPointerException into JDBCStoreQuery To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=20cf307abcf914cc1904d01c52df X-Virus-Checked: Checked by ClamAV on apache.org --20cf307abcf914cc1904d01c52df Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thanks for diving in and getting a testcase. Open a new issue on JIRA. I don't remember offhand whether Slice supports the compilation cache, but I'd rather document it in JIRA than on the mailing list. Worst case we can always improve the documentation in the JIRA.. -mike On Wed, Dec 5, 2012 at 2:36 AM, Fabio Martelli wr= ote: > > Il giorno 05/dic/2012, alle ore 03.48, Michael Dick ha scritto: > > > It seems to me that there are two possible use cases here. > > > > 1.) The Broker has been serialized and deserialized. In this case the > code > > expects that the LifeCycleEventManager will be serialized with the Brok= er > > and the saved LCEventManager should be used from that point on (or at > least > > until free() is called). > > > > To investigate this case it'd be handy to serialize/deserialize the > broker > > and see if the LCEventManager is preserved. If not then perhaps it's a > bug > > in serialization. If it is preserved then the lack of a null check isn'= t > > (necessarily) a red flag. > > > > 2.) The LCEventManager becomes null after doing two bulk delete > operations > > (this was mentioned in the original email). Unless the extension to sli= ce > > or your testcase are serializing the broker this is a different issue. > > > > In either case I'd suggest creating a repeatable testcase, or steps to > > reproduce with 'vanilla' OpenJPA and opening a JIRA. > > Hi Michael, > I'm able to reproduce the problem only if I use slice. > > Actually, it seems that joining the QueryCompilationCache to a slice > configuration cause the problem in object. > > I changed the org.apache.openjpa.slice.TestBasic class in order to > reproduce the problem. Please, take a look at the diff below. > > --- src/test/java/org/apache/openjpa/slice/TestBasic.java (revision > 1415215) > +++ src/test/java/org/apache/openjpa/slice/TestBasic.java (working > copy) > @@ -46,8 +46,14 @@ > > > public void setUp() throws Exception { > - super.setUp(PObject.class, Person.class, Address.class, > Country.class, > + super.setUp("openjpa.QueryCompilationCache", "true", > + PObject.class, Person.class, Address.class, Country.class, > CLEAR_TABLES); > + EntityManager em =3D emf.createEntityManager(); > + em.getTransaction().begin(); > + em.createQuery("DELETE FROM PObject p").executeUpdate(); > + em.getTransaction().commit(); > + em.close(); > } > > > Slice should support QueryCompilationCache, shouldn't it? > Please, let me know if I have to open a new issue on Jira. > > Best regards, > F. > > > -mike > > > > > > On Tue, Dec 4, 2012 at 10:30 AM, Fabio Martelli < > fabio.martelli@gmail.com>wrote: > > > >> > >> Il giorno 04/dic/2012, alle ore 17.05, Rick Curtis ha scritto: > >> > >>> I'm not certain the null check is the correct change.... Why aren't w= e > >>> getting a LifeCycleEventManager on deserialization? > >> > >> Hi Rick, > >> BrokerImpl initialize LifecycleEventManager into the initialize method= . > >> > >> From my PPOV, the piece of code that suggest what I wrote in my email = is > >> the following > >> > >> .... > >> if (!fromDeserialization) { > >> _lifeEventManager =3D _conf.getLifecycleEventManagerInstanc= e(); > >> ..... > >> } > >> ..... > >> > >> Now, fromDeserialization is a method's parameter so someone could > provide > >> a "true" value for it. > >> > >> In particular, the following chain seems to provide a "true" value for > >> fromDeserialization parameter > >> > >> BrokerImpl.readObject =97> AbstractBrokerFactory.initializeBrok= er > =97> > >> BrokerImpl.initialize > >> > >> Please tell me if I wrong or I missed something. > >> > >> Best regards, > >> F. > >> > >> Now, since initialize can be called by BrokerFactory.initializeBroker > >> > >>> Thanks, > >>> Rick > >>> > >>> On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli < > fabio.martelli@gmail.com > >>> wrote: > >>> > >>>> JDBCStoreQuery > >>> > >>> > >>> > >>> > >>> -- > >>> *Rick Curtis* > >> > >> > > --20cf307abcf914cc1904d01c52df-- From dev-return-21335-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 5 16:23:41 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4C7E8DBDF for ; Wed, 5 Dec 2012 16:23:41 +0000 (UTC) Received: (qmail 14071 invoked by uid 500); 5 Dec 2012 15:53:51 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 13529 invoked by uid 500); 5 Dec 2012 15:53:29 -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 13184 invoked by uid 99); 5 Dec 2012 15:53:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 15:53:18 +0000 Date: Wed, 5 Dec 2012 15:53:18 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: <1467017687.63633.1354722798706.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (OPENJPA-2301) NullPointerException using Slice with openjpa.QueryCompilationCache enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 fabio martelli created OPENJPA-2301: --------------------------------------- Summary: NullPointerException using Slice with openjpa.QueryCompilationCache enabled Key: OPENJPA-2301 URL: https://issues.apache.org/jira/browse/OPENJPA-2301 Project: OpenJPA Issue Type: Bug Components: slice Affects Versions: 2.2.1 Reporter: fabio martelli Joining the QueryCompilationCache to a slice configuration cause a NullPointerException. For more detail, please take a look at the ML discussion thread at http://mail-archives.apache.org/mod_mbox/openjpa-dev/201212.mbox/%3CB4582E22-403D-4F4E-BB4C-7F4DB8F1C7BF@gmail.com%3E To reproduce the issue, please patch the class TestBasic as provided below and execute it. --- src/test/java/org/apache/openjpa/slice/TestBasic.java (revision 1415215) +++ src/test/java/org/apache/openjpa/slice/TestBasic.java (working copy) @@ -46,8 +46,14 @@ public void setUp() throws Exception { - super.setUp(PObject.class, Person.class, Address.class, Country.class, + super.setUp("openjpa.QueryCompilationCache", "true", + PObject.class, Person.class, Address.class, Country.class, CLEAR_TABLES); + EntityManager em = emf.createEntityManager(); + em.getTransaction().begin(); + em.createQuery("DELETE FROM PObject p").executeUpdate(); + em.getTransaction().commit(); + em.close(); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21336-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 5 16:23:55 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACE1ADBE7 for ; Wed, 5 Dec 2012 16:23:55 +0000 (UTC) Received: (qmail 19358 invoked by uid 500); 5 Dec 2012 15:57:28 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 19195 invoked by uid 500); 5 Dec 2012 15:57:24 -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 18888 invoked by uid 99); 5 Dec 2012 15:57:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 15:57:12 +0000 Date: Wed, 5 Dec 2012 15:57:12 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: <425145405.63641.1354723032594.JavaMail.jiratomcat@arcas> In-Reply-To: <1467017687.63633.1354722798706.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (OPENJPA-2301) NullPointerException using Slice with openjpa.QueryCompilationCache enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated OPENJPA-2301: ------------------------------------ Description: QueryCompilationCache with a standard slice configuration cause a NullPointerException. For more detail, please take a look at the ML discussion thread at http://mail-archives.apache.org/mod_mbox/openjpa-dev/201212.mbox/%3CB4582E22-403D-4F4E-BB4C-7F4DB8F1C7BF@gmail.com%3E To reproduce the issue, please patch the class TestBasic as provided below and execute it. --- src/test/java/org/apache/openjpa/slice/TestBasic.java (revision 1415215) +++ src/test/java/org/apache/openjpa/slice/TestBasic.java (working copy) @@ -46,8 +46,14 @@ public void setUp() throws Exception { - super.setUp(PObject.class, Person.class, Address.class, Country.class, + super.setUp("openjpa.QueryCompilationCache", "true", + PObject.class, Person.class, Address.class, Country.class, CLEAR_TABLES); + EntityManager em = emf.createEntityManager(); + em.getTransaction().begin(); + em.createQuery("DELETE FROM PObject p").executeUpdate(); + em.getTransaction().commit(); + em.close(); } was: Joining the QueryCompilationCache to a slice configuration cause a NullPointerException. For more detail, please take a look at the ML discussion thread at http://mail-archives.apache.org/mod_mbox/openjpa-dev/201212.mbox/%3CB4582E22-403D-4F4E-BB4C-7F4DB8F1C7BF@gmail.com%3E To reproduce the issue, please patch the class TestBasic as provided below and execute it. --- src/test/java/org/apache/openjpa/slice/TestBasic.java (revision 1415215) +++ src/test/java/org/apache/openjpa/slice/TestBasic.java (working copy) @@ -46,8 +46,14 @@ public void setUp() throws Exception { - super.setUp(PObject.class, Person.class, Address.class, Country.class, + super.setUp("openjpa.QueryCompilationCache", "true", + PObject.class, Person.class, Address.class, Country.class, CLEAR_TABLES); + EntityManager em = emf.createEntityManager(); + em.getTransaction().begin(); + em.createQuery("DELETE FROM PObject p").executeUpdate(); + em.getTransaction().commit(); + em.close(); } > NullPointerException using Slice with openjpa.QueryCompilationCache enabled > --------------------------------------------------------------------------- > > Key: OPENJPA-2301 > URL: https://issues.apache.org/jira/browse/OPENJPA-2301 > Project: OpenJPA > Issue Type: Bug > Components: slice > Affects Versions: 2.2.1 > Reporter: fabio martelli > > QueryCompilationCache with a standard slice configuration cause a NullPointerException. > For more detail, please take a look at the ML discussion thread at http://mail-archives.apache.org/mod_mbox/openjpa-dev/201212.mbox/%3CB4582E22-403D-4F4E-BB4C-7F4DB8F1C7BF@gmail.com%3E > To reproduce the issue, please patch the class TestBasic as provided below and execute it. > --- src/test/java/org/apache/openjpa/slice/TestBasic.java (revision 1415215) > +++ src/test/java/org/apache/openjpa/slice/TestBasic.java (working copy) > @@ -46,8 +46,14 @@ > public void setUp() throws Exception { > - super.setUp(PObject.class, Person.class, Address.class, Country.class, > + super.setUp("openjpa.QueryCompilationCache", "true", > + PObject.class, Person.class, Address.class, Country.class, > CLEAR_TABLES); > + EntityManager em = emf.createEntityManager(); > + em.getTransaction().begin(); > + em.createQuery("DELETE FROM PObject p").executeUpdate(); > + em.getTransaction().commit(); > + em.close(); > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21337-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Dec 6 00:23:50 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6500EE6A6 for ; Thu, 6 Dec 2012 00:23:50 +0000 (UTC) Received: (qmail 48602 invoked by uid 500); 6 Dec 2012 00:23:50 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 48559 invoked by uid 500); 6 Dec 2012 00:23:50 -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 48545 invoked by uid 99); 6 Dec 2012 00:23:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 00:23:49 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.250.139 is neither permitted nor denied by domain of exabrial@gmail.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 00:23:45 +0000 Received: from jim.nabble.com ([192.168.236.80]) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TgPFM-00074x-Df for dev@openjpa.apache.org; Wed, 05 Dec 2012 16:23:24 -0800 Date: Wed, 5 Dec 2012 16:23:24 -0800 (PST) From: exabrial To: dev@openjpa.apache.org Message-ID: <1354753404402-7582053.post@n2.nabble.com> Subject: JPA Profiler to Capture Queries MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello Everyone! I'm trying to create a JPA Profiler for web applications. The idea is to capture all of the queries executed during a web request lifecycle. I was able to get this to work with EclipseLink fairly easily, they have a http://www.eclipse.org/eclipselink/api/2.2/org/eclipse/persistence/sessions/SessionProfiler.html class that I could use a decorator pattern to monitor the queries executed on the current thread. I need a bit of help creating an adapter for OpenJPA. I need to be notified somehow when a query is about to be executed and when the execution is finished. I'm having a bit of trouble locating an API to do this inside OpenJPA. Can someone point me in the right direction? Ideally, I'd like to be able to specify something inside the JPA properties section that would activate the query capture. Thanks a ton guys, cheers! -Jonathan -- View this message in context: http://openjpa.208410.n2.nabble.com/JPA-Profiler-to-Capture-Queries-tp7582053.html Sent from the OpenJPA Developers mailing list archive at Nabble.com. From dev-return-21338-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Dec 6 15:25:39 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 829CDE9B9 for ; Thu, 6 Dec 2012 15:25:39 +0000 (UTC) Received: (qmail 30019 invoked by uid 500); 6 Dec 2012 15:25:38 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 29762 invoked by uid 500); 6 Dec 2012 15:25:34 -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 29662 invoked by uid 99); 6 Dec 2012 15:25:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 15:25:33 +0000 X-ASF-Spam-Status: No, hits=3.1 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of curtisr7@gmail.com designates 209.85.217.174 as permitted sender) Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 15:25:26 +0000 Received: by mail-lb0-f174.google.com with SMTP id gi11so6021630lbb.33 for ; Thu, 06 Dec 2012 07:25:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Zhk6T86X00wE59qlgkYs9sy8QRWEQjdJmGsKRmyyTYw=; b=PsCnew2WJyFM1x1EwBzrB1B+XkyWRmLHGmOFRY7xEUCJ4l8y2FthRsqBvCtC2HyVgC yzpXkut2hI/R+T93tZNvq/TBXIZG3Duqvflcf9pCFa0lZBEFMDykO752iaSFk5kZvDDX Y8ijWZHL9KguYydXHhbkKfjyykbtzFq/mzfAl2dlB3tW0vXs8uH99zgv2VoVFL8kKNwq RgEsibs/vtVWQV1aN+2yTYT7aw39CGnJhI7Jeebny4kS0Yfb7ufPHZYjBK+W5n2lsnZ8 Hl09xLzPbAqXNbcaM6mLPvnlr8dB4Tb55B42nSe3SwE75UFMc3f0Q55fqGuAx+W6bj/0 WIWg== MIME-Version: 1.0 Received: by 10.152.108.48 with SMTP id hh16mr2042197lab.25.1354807505608; Thu, 06 Dec 2012 07:25:05 -0800 (PST) Received: by 10.114.13.199 with HTTP; Thu, 6 Dec 2012 07:25:05 -0800 (PST) In-Reply-To: <1354753404402-7582053.post@n2.nabble.com> References: <1354753404402-7582053.post@n2.nabble.com> Date: Thu, 6 Dec 2012 09:25:05 -0600 Message-ID: Subject: Re: JPA Profiler to Capture Queries From: Rick Curtis To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=bcaec54fb9d21c5f8404d030b4f4 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54fb9d21c5f8404d030b4f4 Content-Type: text/plain; charset=ISO-8859-1 Take a look at JDBCListeners[1] [1] http://openjpa.apache.org/builds/latest/docs/docbook/manual.html#openjpa.jdbc.JDBCListeners Thanks, Rick On Wed, Dec 5, 2012 at 6:23 PM, exabrial wrote: > Hello Everyone! > > I'm trying to create a JPA Profiler for web applications. The idea is to > capture all of the queries executed during a web request lifecycle. > > I was able to get this to work with EclipseLink fairly easily, they have a > > http://www.eclipse.org/eclipselink/api/2.2/org/eclipse/persistence/sessions/SessionProfiler.html > class that I could use a decorator pattern to monitor the queries executed > on the current thread. > > I need a bit of help creating an adapter for OpenJPA. I need to be notified > somehow when a query is about to be executed and when the execution is > finished. I'm having a bit of trouble locating an API to do this inside > OpenJPA. Can someone point me in the right direction? Ideally, I'd like to > be able to specify something inside the JPA properties section that would > activate the query capture. > > Thanks a ton guys, cheers! > -Jonathan > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/JPA-Profiler-to-Capture-Queries-tp7582053.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. > -- *Rick Curtis* --bcaec54fb9d21c5f8404d030b4f4-- From dev-return-21339-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Fri Dec 7 18:52:43 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70660EC52 for ; Fri, 7 Dec 2012 18:52:43 +0000 (UTC) Received: (qmail 12864 invoked by uid 500); 7 Dec 2012 18:52:43 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 12796 invoked by uid 500); 7 Dec 2012 18:52:42 -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 12787 invoked by uid 99); 7 Dec 2012 18:52:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 18:52:42 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.250.139 is neither permitted nor denied by domain of exabrial@gmail.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 18:52:37 +0000 Received: from jim.nabble.com ([192.168.236.80]) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Th320-0006Qw-Co for dev@openjpa.apache.org; Fri, 07 Dec 2012 10:52:16 -0800 Date: Fri, 7 Dec 2012 10:52:16 -0800 (PST) From: exabrial To: dev@openjpa.apache.org Message-ID: <1354906336353-7582062.post@n2.nabble.com> In-Reply-To: References: <1354753404402-7582053.post@n2.nabble.com> Subject: Re: JPA Profiler to Capture Queries MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Thanks a ton Rick! That class definitely got me the basic information, and I was easily able to implement a query timer. I have a followup question: If the current query being executed is a named query, is there a way to grab it's name? The idea being that I'm displaying pie charts to the user of time spent in each query, and I want to give them the ability to correlate the SQL back to the uncompiled JPQL. Once again thankyou! -- View this message in context: http://openjpa.208410.n2.nabble.com/JPA-Profiler-to-Capture-Queries-tp7582053p7582062.html Sent from the OpenJPA Developers mailing list archive at Nabble.com. From dev-return-21340-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Sun Dec 9 14:03:38 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46A15D0FD for ; Sun, 9 Dec 2012 14:03:38 +0000 (UTC) Received: (qmail 80255 invoked by uid 500); 9 Dec 2012 14:03:38 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 80017 invoked by uid 500); 9 Dec 2012 14:03:34 -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 79920 invoked by uid 99); 9 Dec 2012 14:03:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2012 14:03:32 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [77.238.189.66] (HELO nm13.bullet.mail.ird.yahoo.com) (77.238.189.66) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2012 14:03:26 +0000 Received: from [77.238.189.231] by nm13.bullet.mail.ird.yahoo.com with NNFMP; 09 Dec 2012 14:03:04 -0000 Received: from [212.82.108.135] by tm12.bullet.mail.ird.yahoo.com with NNFMP; 09 Dec 2012 14:03:03 -0000 Received: from [127.0.0.1] by omp1040.mail.ird.yahoo.com with NNFMP; 09 Dec 2012 14:03:03 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 889879.46239.bm@omp1040.mail.ird.yahoo.com Received: (qmail 19382 invoked by uid 60001); 9 Dec 2012 14:03:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.de; s=s1024; t=1355061783; bh=z/PP8pHiE9td9dK+Goi7eTosBrp4laBk7pVq62s0Dgo=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=oxF9mBdvah+FxgmjmUmgntuJpMU+33ssaEd4bv73zfnYt5KowJpyaoFgQhAn7i/feu8ubuiu3bAWo1i8EtSnwrSGRDaSSM8vH+SxaNhqSrcrLwkDNv2/XhXK8shFrfza6tHHRpFhODKhegCjvUlIZnkTFwq4JfdqzP3ARDArjMo= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RXrqERE7PXI9IjZloB+dpC6Hfcer6YzKNEN1Pv0ILPtDpK5ZKcl1P2I3qV4PltXuSCD/GRVs0ZMGy8PxLFapmBmUiJw83+2KbdZ2i+kVYBs5WNG88Wm7FubyHL3jv5hnR2gViflV2VYTuFFZtAkF/unrw6Uu7yupMaNcczVeJHY=; X-YMail-OSG: f.iUlXcVM1m0ZqS07n_NzbmRgWJCps5Xx6Q4kq8l9JMgEf4 hzNOXf4Lqnnc2mz9idbLIl2UMhpK8Df5dlijMxU50IHHlG0xQ9ElTsbglHhl E5Htrb4xZXtYHukfsu664kecxQCW7RahZw8if4iNwF5pnhoJ9aoMnl3U7VDN ottzNmvSk5xYgYsBbf9Tt6vv1N0Syqak2gcmCPEqci3c3AxMQ1jr.w3jSY8P m6Li9MzJ7NLwP4VAjmLCmR8nukdcjSJOXuqA.ohKqNFvjcCAdfqb3FvGKeyN caPsU28v7Q9ueRczpw2nMMYSqykJE5st0RNOrLWx89wcSgVaoOs2vSGneHCq g5HcfOEWUeHPn_jplay.VJwUE5gQcGgHiyZzJPK1v5K0qINLon7DjJSUff.N tZYN4WaYxbr1iblPIrqq0QQFpoQ_TVRM6eT8ZYycNvbzp36pRz0NcjlllYiI lb6IJ0D2SZwjcX7YABSbJynLQkZJ5bogjOTSY.ff4PmZ7zWUUkfQ2azGD4BU KM4Xzux5r0RCnY9Rajkc3KLyXJmTpr_W0qyZtAMiiLWcFqGk3.UNImiZoZyb InAK6lt6DQvTAmwfa0mZRhg-- Received: from [80.108.122.184] by web28902.mail.ir2.yahoo.com via HTTP; Sun, 09 Dec 2012 14:03:03 GMT X-Rocket-MIMEInfo: 001.001,QmVpbmcgdmVyeSBhY3RpdmUgaW4gT3BlbldlYkJlYW5zIGFuZCBldmVuIGEgQ0RJIEVHIG1lbWJlciBJIGNhbiBoZWxwIG91dCB3aXRoIHRoZSBDREkgcGFydHMuwqAKCkxpZUdydWUsCnN0cnViCgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBLZXZpbiBTdXR0ZXIgPGt3c3V0dGVyQGdtYWlsLmNvbT4KPiBUbzogZGV2QG9wZW5qcGEuYXBhY2hlLm9yZzsgdXNlcnNAb3BlbmpwYS5hcGFjaGUub3JnCj4gQ2M6IAo.IFNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAyOSwgMjAxMiA0OjA4IFABMAEBAQE- X-Mailer: YahooMailWebService/0.8.128.478 References: Message-ID: <1355061783.13321.YahooMailNeo@web28902.mail.ir2.yahoo.com> Date: Sun, 9 Dec 2012 14:03:03 +0000 (GMT) From: Mark Struberg Reply-To: Mark Struberg Subject: Re: [DISCUSSION] JPA 2.1 spec implementation To: "dev@openjpa.apache.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Being very active in OpenWebBeans and even a CDI EG member I can help out w= ith the CDI parts.=A0=0A=0ALieGrue,=0Astrub=0A=0A=0A=0A----- Original Messa= ge -----=0A> From: Kevin Sutter =0A> To: dev@openjpa.ap= ache.org; users@openjpa.apache.org=0A> Cc: =0A> Sent: Thursday, November 29= , 2012 4:08 PM=0A> Subject: [DISCUSSION] JPA 2.1 spec implementation=0A> = =0A> Hi,=0A> Recently, JSR 338 released the Early Draft Review #2 of the JP= A 2.1=0A> specification.=A0 You can access this latest version of the speci= fication via=0A> this URL:=0A> =0A> http://jcp.org/aboutJava/communityproce= ss/edr/jsr338/index2.html=0A> =0A> As you'll notice this version of the spe= c will close for comments tomorrow,=0A> Nov 30.=A0 This date is actually ju= st a formality, since you can submit=0A> comments after this date.=A0 Any s= uch late comments would not be applied to=0A> this particular version of th= e document, that's all.=0A> =0A> Anyway, the review of the specification, a= lthough important, is not the=0A> point of this message.=A0 The point of th= is message is to gauge the community=0A> interest in this updated version o= f the JPA 2.1 specification.=A0 As we=0A> experienced with the JPA 2.0 deli= very, the implementation of a new=0A> specification takes a lot of effort.= =A0 And, although our user community for=0A> OpenJPA continues to grow and = expand, the development community has not had=0A> the same luxury.=A0 We do= still have a core group of developers that are=0A> heavily engaged in day-= to-day activities with OpenJPA (forums, fixes,=0A> performance features, do= c updates, tooling, release mgmt, etc).=A0 But, we=0A> will need even more = assistance when we take on the development of JPA 2.1.=0A> =0A> As a little= background for those of you new to the project (since JPA 2.0),=0A> at thi= s point in the development of the JPA 2.0 specification, our OpenJPA=0A> te= am was already deep into the implementation of the early drafts of that=0A>= specification.=A0 Of course, the RI was the first implementation of JPA 2.= 0=0A> after the spec finalized, but OpenJPA 2.0 was a very close second (wi= thin=0A> weeks of the spec going final).=A0 We were all very proud of that= =0A> accomplishment.=0A> =0A> JPA 2.1 is targeted for an early 2013 final s= pecification.=A0 The point of=0A> this note is to gauge the community inter= est in this new specification, and=0A> to gauge the interest of the develop= ment community to aid with the=0A> implementation and testing of this speci= fication.=0A> =0A> Thank you for all of your contributions!=0A> =0A> Kevin= =0A> =0A> P.S.=A0 Here are some cliff notes for the highlights in the JPA 2= .1=0A> specification (some of which are already provided by OpenJPA in one = form or=0A> another):=0A> o=A0 Formal Stored Procedure support=0A> o=A0 Syn= chronizationType to control when to enlist with transaction=0A> o=A0 CDI su= pport for Entity Listeners=0A> o=A0 Type Conversions (similar to OpenJPA's = Externalizer)=0A> o=A0 Further explanation of how to return managed and unm= anaged data from=0A> NativeQueries=0A> o=A0 JPQL updates=0A> o=A0 Support f= or TREAT (downcasting)=0A> o=A0 Criteria API refactoring (hopefully just in= ternal impacts)=0A> o=A0 Allow use of packaged scripts:=A0 ddl-create-scrip= t, ddl-drop-script,=0A> ddl-load-script=0A> o=A0 Schema generation (similar= to OpenJPA's capability)=0A> o=A0 Annotation updates:=A0 @Converter, @Fore= ignKey, @Index=0A> From dev-return-21341-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 11:19:29 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A1866D356 for ; Mon, 10 Dec 2012 11:19:29 +0000 (UTC) Received: (qmail 81316 invoked by uid 500); 10 Dec 2012 11:19:29 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 80908 invoked by uid 500); 10 Dec 2012 11:19:24 -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 80316 invoked by uid 99); 10 Dec 2012 11:19:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 11:19:22 +0000 Date: Mon, 10 Dec 2012 11:19:22 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2302) Slice support for QueryCompilationCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 fabio martelli created OPENJPA-2302: --------------------------------------- Summary: Slice support for QueryCompilationCache Key: OPENJPA-2302 URL: https://issues.apache.org/jira/browse/OPENJPA-2302 Project: OpenJPA Issue Type: Improvement Components: slice Affects Versions: 2.2.1, 2.3.0 Reporter: fabio martelli Fix For: 2.3.0 It seems that slice doesn't support QueryCompilationCache. By running the following test case ... public class TestQueryCompilationCache extends SliceTestCase { /** * Specify persistence unit name as System property * -Dunit or use the default value as * "slice". */ protected String getPersistenceUnitName() { return System.getProperty("unit", "slice"); } @Override public void setUp() { super.setUp(PObject.class, "openjpa.QueryCompilationCache", "true"); } public void testQueryCompilationCache() throws Exception { OpenJPAEntityManager em = emf.createEntityManager(); em.getTransaction().begin(); em.createQuery("SELECT o from PObject o").getResultList(); em.getTransaction().commit(); em.close(); em = emf.createEntityManager(); em.createQuery("SELECT o from PObject o").getResultList(); em.close(); emf.close(); } } The following exception will be raised. testQueryCompilationCache(org.apache.openjpa.slice.TestQueryCompilationCache) Time elapsed: 1.923 sec <<< ERROR! org.apache.openjpa.persistence.PersistenceException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$ParallelExecutor.executeQuery(DistributedStoreQuery.java:156) at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005) at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863) at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794) at org.apache.openjpa.slice.DistributedQueryImpl.execute(DistributedQueryImpl.java:61) at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542) at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286) at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302) at org.apache.openjpa.slice.TestQueryCompilationCache.testQueryCompilationCache(TestQueryCompilationCache.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.apache.openjpa.slice.PersistenceTestCase.run(PersistenceTestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) at org.apache.maven.surefire.Surefire.run(Surefire.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) Caused by: org.apache.openjpa.persistence.InvalidStateException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. at org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:4683) at org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:1700) at org.apache.openjpa.kernel.QueryImpl.isUnique(QueryImpl.java:453) at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.calculateEagerMode(JDBCStoreQuery.java:483) at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeQuery(JDBCStoreQuery.java:174) at org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeQuery(ExpressionStoreQuery.java:783) at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:273) at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:266) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21342-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 11:39:24 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8E98DE13B for ; Mon, 10 Dec 2012 11:39:24 +0000 (UTC) Received: (qmail 24606 invoked by uid 500); 10 Dec 2012 11:39:24 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 24547 invoked by uid 500); 10 Dec 2012 11:39:24 -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 24405 invoked by uid 99); 10 Dec 2012 11:39:23 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 11:39:23 +0000 Date: Mon, 10 Dec 2012 11:39:22 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2302) Slice support for QueryCompilationCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated OPENJPA-2302: ------------------------------------ Attachment: patch.diff This patch should add QueryCompilationCache support to slice ... > Slice support for QueryCompilationCache > --------------------------------------- > > Key: OPENJPA-2302 > URL: https://issues.apache.org/jira/browse/OPENJPA-2302 > Project: OpenJPA > Issue Type: Improvement > Components: slice > Affects Versions: 2.3.0, 2.2.1 > Reporter: fabio martelli > Fix For: 2.3.0 > > Attachments: patch.diff > > > It seems that slice doesn't support QueryCompilationCache. > By running the following test case ... > public class TestQueryCompilationCache extends SliceTestCase { > /** > * Specify persistence unit name as System property > * -Dunit or use the default value as > * "slice". > */ > protected String getPersistenceUnitName() { > return System.getProperty("unit", "slice"); > } > @Override > public void setUp() { > super.setUp(PObject.class, > "openjpa.QueryCompilationCache", "true"); > } > public void testQueryCompilationCache() > throws Exception { > OpenJPAEntityManager em = emf.createEntityManager(); > em.getTransaction().begin(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.getTransaction().commit(); > em.close(); > em = emf.createEntityManager(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.close(); > emf.close(); > } > } > The following exception will be raised. > testQueryCompilationCache(org.apache.openjpa.slice.TestQueryCompilationCache) Time elapsed: 1.923 sec <<< ERROR! > org.apache.openjpa.persistence.PersistenceException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$ParallelExecutor.executeQuery(DistributedStoreQuery.java:156) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794) > at org.apache.openjpa.slice.DistributedQueryImpl.execute(DistributedQueryImpl.java:61) > at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542) > at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286) > at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302) > at org.apache.openjpa.slice.TestQueryCompilationCache.testQueryCompilationCache(TestQueryCompilationCache.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at org.apache.openjpa.slice.PersistenceTestCase.run(PersistenceTestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: org.apache.openjpa.persistence.InvalidStateException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:4683) > at org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:1700) > at org.apache.openjpa.kernel.QueryImpl.isUnique(QueryImpl.java:453) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.calculateEagerMode(JDBCStoreQuery.java:483) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeQuery(JDBCStoreQuery.java:174) > at org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeQuery(ExpressionStoreQuery.java:783) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:273) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:266) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21343-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 11:46:52 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C5E7E15F for ; Mon, 10 Dec 2012 11:46:52 +0000 (UTC) Received: (qmail 41803 invoked by uid 500); 10 Dec 2012 11:46:52 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 41630 invoked by uid 500); 10 Dec 2012 11:46:52 -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 41618 invoked by uid 99); 10 Dec 2012 11:46:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 11:46:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fabio.martelli@gmail.com designates 209.85.214.46 as permitted sender) Received: from [209.85.214.46] (HELO mail-bk0-f46.google.com) (209.85.214.46) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 11:46:41 +0000 Received: by mail-bk0-f46.google.com with SMTP id q16so1106054bkw.33 for ; Mon, 10 Dec 2012 03:46:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; bh=ZkaQjRd5KKEUBID3Nxaqp0eUfHxuow2gG1zIqrzghUQ=; b=v50qpGAToNIqbxyk8EjKTvdY/C3TVFh3RJeJPcf7UylL//XxzRTXZyZKqa1ch7zz1d HUjOkv+Pk6ir0gxj4xfX8a91srGzKJSR80bGzbSu8TE6Vwnm+L5Cc7p1NfWqKtMqY5sX cEY+1l1f0qTOVtBbNt4oHzLFe4tlDmvev2eNq2pVKj8kJSYoDdYZJS9C6ClRJHEWHIyR wcJgbtUcZ839SLBYTIKQ6DdUM/RfAzwSusrECDGRh4yDfiDpr2KATiSdaDsDSpZWreCh 3JwytwyjHJElhrq9RVI2ruw4JB273oOSWx9OCxq9zpOMN8/NssHKVQO2ZZtSnWqJEbez Mj2Q== Received: by 10.204.150.218 with SMTP id z26mr4381700bkv.95.1355139980542; Mon, 10 Dec 2012 03:46:20 -0800 (PST) Received: from macpro.pluto.org (rovere.tirasa.net. [78.134.5.44]) by mx.google.com with ESMTPS id d16sm13688653bkw.2.2012.12.10.03.46.18 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 10 Dec 2012 03:46:19 -0800 (PST) From: Fabio Martelli Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: multipart/alternative; boundary=Apple-Mail-14-1023138497 Subject: Re: NullPointerException into JDBCStoreQuery Date: Mon, 10 Dec 2012 12:46:16 +0100 In-Reply-To: To: dev@openjpa.apache.org References: <8F7344F8-C8AE-42B6-AF4C-B684C7AD22CD@gmail.com> <7248D85C-47D5-49E0-B371-216CB07A752C@gmail.com> Message-Id: <431CF6B6-0C7F-4569-899F-C7D488163BBE@gmail.com> X-Mailer: Apple Mail (2.1085) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-14-1023138497 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Il giorno 05/dic/2012, alle ore 16.05, Michael Dick ha scritto: > Thanks for diving in and getting a testcase. >=20 > Open a new issue on JIRA. I don't remember offhand whether Slice = supports > the compilation cache, but I'd rather document it in JIRA than on the > mailing list. >=20 > Worst case we can always improve the documentation in the JIRA.. Hi Guys, it seems that slice doesn't support QueryCompilationCache ... I opened the following two issues related to this problem.=20 https://issues.apache.org/jira/browse/OPENJPA-2301 https://issues.apache.org/jira/browse/OPENJPA-2302 I hope someone can take a look at the last provided patch (attached to = OPENJPA-2302). Best regards, F. >=20 > -mike >=20 >=20 > On Wed, Dec 5, 2012 at 2:36 AM, Fabio Martelli = wrote: >=20 >>=20 >> Il giorno 05/dic/2012, alle ore 03.48, Michael Dick ha scritto: >>=20 >>> It seems to me that there are two possible use cases here. >>>=20 >>> 1.) The Broker has been serialized and deserialized. In this case = the >> code >>> expects that the LifeCycleEventManager will be serialized with the = Broker >>> and the saved LCEventManager should be used from that point on (or = at >> least >>> until free() is called). >>>=20 >>> To investigate this case it'd be handy to serialize/deserialize the >> broker >>> and see if the LCEventManager is preserved. If not then perhaps it's = a >> bug >>> in serialization. If it is preserved then the lack of a null check = isn't >>> (necessarily) a red flag. >>>=20 >>> 2.) The LCEventManager becomes null after doing two bulk delete >> operations >>> (this was mentioned in the original email). Unless the extension to = slice >>> or your testcase are serializing the broker this is a different = issue. >>>=20 >>> In either case I'd suggest creating a repeatable testcase, or steps = to >>> reproduce with 'vanilla' OpenJPA and opening a JIRA. >>=20 >> Hi Michael, >> I'm able to reproduce the problem only if I use slice. >>=20 >> Actually, it seems that joining the QueryCompilationCache to a slice >> configuration cause the problem in object. >>=20 >> I changed the org.apache.openjpa.slice.TestBasic class in order to >> reproduce the problem. Please, take a look at the diff below. >>=20 >> --- src/test/java/org/apache/openjpa/slice/TestBasic.java = (revision >> 1415215) >> +++ src/test/java/org/apache/openjpa/slice/TestBasic.java = (working >> copy) >> @@ -46,8 +46,14 @@ >>=20 >>=20 >> public void setUp() throws Exception { >> - super.setUp(PObject.class, Person.class, Address.class, >> Country.class, >> + super.setUp("openjpa.QueryCompilationCache", "true", >> + PObject.class, Person.class, Address.class, = Country.class, >> CLEAR_TABLES); >> + EntityManager em =3D emf.createEntityManager(); >> + em.getTransaction().begin(); >> + em.createQuery("DELETE FROM PObject p").executeUpdate(); >> + em.getTransaction().commit(); >> + em.close(); >> } >>=20 >>=20 >> Slice should support QueryCompilationCache, shouldn't it? >> Please, let me know if I have to open a new issue on Jira. >>=20 >> Best regards, >> F. >>=20 >>> -mike >>>=20 >>>=20 >>> On Tue, Dec 4, 2012 at 10:30 AM, Fabio Martelli < >> fabio.martelli@gmail.com>wrote: >>>=20 >>>>=20 >>>> Il giorno 04/dic/2012, alle ore 17.05, Rick Curtis ha scritto: >>>>=20 >>>>> I'm not certain the null check is the correct change.... Why = aren't we >>>>> getting a LifeCycleEventManager on deserialization? >>>>=20 >>>> Hi Rick, >>>> BrokerImpl initialize LifecycleEventManager into the initialize = method. >>>>=20 >>>> =46rom my PPOV, the piece of code that suggest what I wrote in my = email is >>>> the following >>>>=20 >>>> .... >>>> if (!fromDeserialization) { >>>> _lifeEventManager =3D = _conf.getLifecycleEventManagerInstance(); >>>> ..... >>>> } >>>> ..... >>>>=20 >>>> Now, fromDeserialization is a method's parameter so someone could >> provide >>>> a "true" value for it. >>>>=20 >>>> In particular, the following chain seems to provide a "true" value = for >>>> fromDeserialization parameter >>>>=20 >>>> BrokerImpl.readObject =97> = AbstractBrokerFactory.initializeBroker >> =97> >>>> BrokerImpl.initialize >>>>=20 >>>> Please tell me if I wrong or I missed something. >>>>=20 >>>> Best regards, >>>> F. >>>>=20 >>>> Now, since initialize can be called by = BrokerFactory.initializeBroker >>>>=20 >>>>> Thanks, >>>>> Rick >>>>>=20 >>>>> On Tue, Dec 4, 2012 at 3:49 AM, Fabio Martelli < >> fabio.martelli@gmail.com >>>>> wrote: >>>>>=20 >>>>>> JDBCStoreQuery >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> *Rick Curtis* >>>>=20 >>>>=20 >>=20 >>=20 --Apple-Mail-14-1023138497-- From dev-return-21345-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 12:11:23 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DB1CE217 for ; Mon, 10 Dec 2012 12:11:23 +0000 (UTC) Received: (qmail 94260 invoked by uid 500); 10 Dec 2012 12:11:23 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 94043 invoked by uid 500); 10 Dec 2012 12:11: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 93982 invoked by uid 99); 10 Dec 2012 12:11:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 12:11:21 +0000 Date: Mon, 10 Dec 2012 12:11:21 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2302) Slice support for QueryCompilationCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated OPENJPA-2302: ------------------------------------ Attachment: (was: patch.diff) > Slice support for QueryCompilationCache > --------------------------------------- > > Key: OPENJPA-2302 > URL: https://issues.apache.org/jira/browse/OPENJPA-2302 > Project: OpenJPA > Issue Type: Improvement > Components: slice > Affects Versions: 2.3.0, 2.2.1 > Reporter: fabio martelli > Fix For: 2.3.0 > > Attachments: patch.diff > > > It seems that slice doesn't support QueryCompilationCache. > By running the following test case ... > public class TestQueryCompilationCache extends SliceTestCase { > /** > * Specify persistence unit name as System property > * -Dunit or use the default value as > * "slice". > */ > protected String getPersistenceUnitName() { > return System.getProperty("unit", "slice"); > } > @Override > public void setUp() { > super.setUp(PObject.class, > "openjpa.QueryCompilationCache", "true"); > } > public void testQueryCompilationCache() > throws Exception { > OpenJPAEntityManager em = emf.createEntityManager(); > em.getTransaction().begin(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.getTransaction().commit(); > em.close(); > em = emf.createEntityManager(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.close(); > emf.close(); > } > } > The following exception will be raised. > testQueryCompilationCache(org.apache.openjpa.slice.TestQueryCompilationCache) Time elapsed: 1.923 sec <<< ERROR! > org.apache.openjpa.persistence.PersistenceException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$ParallelExecutor.executeQuery(DistributedStoreQuery.java:156) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794) > at org.apache.openjpa.slice.DistributedQueryImpl.execute(DistributedQueryImpl.java:61) > at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542) > at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286) > at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302) > at org.apache.openjpa.slice.TestQueryCompilationCache.testQueryCompilationCache(TestQueryCompilationCache.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at org.apache.openjpa.slice.PersistenceTestCase.run(PersistenceTestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: org.apache.openjpa.persistence.InvalidStateException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:4683) > at org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:1700) > at org.apache.openjpa.kernel.QueryImpl.isUnique(QueryImpl.java:453) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.calculateEagerMode(JDBCStoreQuery.java:483) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeQuery(JDBCStoreQuery.java:174) > at org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeQuery(ExpressionStoreQuery.java:783) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:273) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:266) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21344-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 12:11:24 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F5F5E218 for ; Mon, 10 Dec 2012 12:11:23 +0000 (UTC) Received: (qmail 94214 invoked by uid 500); 10 Dec 2012 12:11:23 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 94036 invoked by uid 500); 10 Dec 2012 12:11: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 93993 invoked by uid 99); 10 Dec 2012 12:11:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 12:11:21 +0000 Date: Mon, 10 Dec 2012 12:11:21 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2302) Slice support for QueryCompilationCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated OPENJPA-2302: ------------------------------------ Attachment: patch.diff > Slice support for QueryCompilationCache > --------------------------------------- > > Key: OPENJPA-2302 > URL: https://issues.apache.org/jira/browse/OPENJPA-2302 > Project: OpenJPA > Issue Type: Improvement > Components: slice > Affects Versions: 2.3.0, 2.2.1 > Reporter: fabio martelli > Fix For: 2.3.0 > > Attachments: patch.diff > > > It seems that slice doesn't support QueryCompilationCache. > By running the following test case ... > public class TestQueryCompilationCache extends SliceTestCase { > /** > * Specify persistence unit name as System property > * -Dunit or use the default value as > * "slice". > */ > protected String getPersistenceUnitName() { > return System.getProperty("unit", "slice"); > } > @Override > public void setUp() { > super.setUp(PObject.class, > "openjpa.QueryCompilationCache", "true"); > } > public void testQueryCompilationCache() > throws Exception { > OpenJPAEntityManager em = emf.createEntityManager(); > em.getTransaction().begin(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.getTransaction().commit(); > em.close(); > em = emf.createEntityManager(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.close(); > emf.close(); > } > } > The following exception will be raised. > testQueryCompilationCache(org.apache.openjpa.slice.TestQueryCompilationCache) Time elapsed: 1.923 sec <<< ERROR! > org.apache.openjpa.persistence.PersistenceException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$ParallelExecutor.executeQuery(DistributedStoreQuery.java:156) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794) > at org.apache.openjpa.slice.DistributedQueryImpl.execute(DistributedQueryImpl.java:61) > at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542) > at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286) > at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302) > at org.apache.openjpa.slice.TestQueryCompilationCache.testQueryCompilationCache(TestQueryCompilationCache.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at org.apache.openjpa.slice.PersistenceTestCase.run(PersistenceTestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: org.apache.openjpa.persistence.InvalidStateException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:4683) > at org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:1700) > at org.apache.openjpa.kernel.QueryImpl.isUnique(QueryImpl.java:453) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.calculateEagerMode(JDBCStoreQuery.java:483) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeQuery(JDBCStoreQuery.java:174) > at org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeQuery(ExpressionStoreQuery.java:783) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:273) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:266) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21347-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 14:19:39 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0E88EE14D for ; Mon, 10 Dec 2012 14:19:39 +0000 (UTC) Received: (qmail 44328 invoked by uid 500); 10 Dec 2012 14:19:38 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 44297 invoked by uid 500); 10 Dec 2012 14:19:38 -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 44286 invoked by uid 99); 10 Dec 2012 14:19:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 14:19:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates 209.85.217.174 as permitted sender) Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 14:19:34 +0000 Received: by mail-lb0-f174.google.com with SMTP id gi11so2347420lbb.33 for ; Mon, 10 Dec 2012 06:19:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=x732OzjP5IMZ3nu80Fuhm9XKEYv3En/42RGG85jbnnk=; b=S5NTcgozRCzoTX+VfvnQQ0nYSA1NRPzoq2Zz1TLYaTgrdWLFUjXE2ooyXuBoM8S+ww 8AxUfsDBkcxbuCqB8RwH543miQRNMsHUyQVgfmqlvS8mtkwp0idYW8HayQPtrrCl2xG2 /8NLkA9Ypk+LK0vcNI5i5T1fjMMGvF/goJyWZJ0wK1KrdnbJcIQZ9b4DYw9QitXRPgXP RdNJdpDwRzMC30GUihKDi6OftBQVdvcKWQmx8b5yW8UKr/CDpoPsAkBheX0J0FDBygQN Cng7CkTgwEM51VM9kQNiZQZEkhPM4hs8vD46jviu4efjAPvnnk8wSJjtwFAwCJdqrCrJ 0Yaw== Received: by 10.152.148.40 with SMTP id tp8mr13981901lab.30.1355149152541; Mon, 10 Dec 2012 06:19:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.111.132 with HTTP; Mon, 10 Dec 2012 06:18:52 -0800 (PST) In-Reply-To: <1355061783.13321.YahooMailNeo@web28902.mail.ir2.yahoo.com> References: <1355061783.13321.YahooMailNeo@web28902.mail.ir2.yahoo.com> From: Kevin Sutter Date: Mon, 10 Dec 2012 08:18:52 -0600 Message-ID: Subject: Re: [DISCUSSION] JPA 2.1 spec implementation To: dev@openjpa.apache.org, Mark Struberg Content-Type: multipart/alternative; boundary=e89a8f234665dadbcc04d0803f0b X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f234665dadbcc04d0803f0b Content-Type: text/plain; charset=ISO-8859-1 This would be very helpful, Mark. My CDI experience is limited, at best. Kevin On Sun, Dec 9, 2012 at 8:03 AM, Mark Struberg wrote: > Being very active in OpenWebBeans and even a CDI EG member I can help out > with the CDI parts. > > LieGrue, > strub > > > > ----- Original Message ----- > > From: Kevin Sutter > > To: dev@openjpa.apache.org; users@openjpa.apache.org > > Cc: > > Sent: Thursday, November 29, 2012 4:08 PM > > Subject: [DISCUSSION] JPA 2.1 spec implementation > > > > Hi, > > Recently, JSR 338 released the Early Draft Review #2 of the JPA 2.1 > > specification. You can access this latest version of the specification > via > > this URL: > > > > http://jcp.org/aboutJava/communityprocess/edr/jsr338/index2.html > > > > As you'll notice this version of the spec will close for comments > tomorrow, > > Nov 30. This date is actually just a formality, since you can submit > > comments after this date. Any such late comments would not be applied to > > this particular version of the document, that's all. > > > > Anyway, the review of the specification, although important, is not the > > point of this message. The point of this message is to gauge the > community > > interest in this updated version of the JPA 2.1 specification. As we > > experienced with the JPA 2.0 delivery, the implementation of a new > > specification takes a lot of effort. And, although our user community > for > > OpenJPA continues to grow and expand, the development community has not > had > > the same luxury. We do still have a core group of developers that are > > heavily engaged in day-to-day activities with OpenJPA (forums, fixes, > > performance features, doc updates, tooling, release mgmt, etc). But, we > > will need even more assistance when we take on the development of JPA > 2.1. > > > > As a little background for those of you new to the project (since JPA > 2.0), > > at this point in the development of the JPA 2.0 specification, our > OpenJPA > > team was already deep into the implementation of the early drafts of that > > specification. Of course, the RI was the first implementation of JPA 2.0 > > after the spec finalized, but OpenJPA 2.0 was a very close second (within > > weeks of the spec going final). We were all very proud of that > > accomplishment. > > > > JPA 2.1 is targeted for an early 2013 final specification. The point of > > this note is to gauge the community interest in this new specification, > and > > to gauge the interest of the development community to aid with the > > implementation and testing of this specification. > > > > Thank you for all of your contributions! > > > > Kevin > > > > P.S. Here are some cliff notes for the highlights in the JPA 2.1 > > specification (some of which are already provided by OpenJPA in one form > or > > another): > > o Formal Stored Procedure support > > o SynchronizationType to control when to enlist with transaction > > o CDI support for Entity Listeners > > o Type Conversions (similar to OpenJPA's Externalizer) > > o Further explanation of how to return managed and unmanaged data from > > NativeQueries > > o JPQL updates > > o Support for TREAT (downcasting) > > o Criteria API refactoring (hopefully just internal impacts) > > o Allow use of packaged scripts: ddl-create-script, ddl-drop-script, > > ddl-load-script > > o Schema generation (similar to OpenJPA's capability) > > o Annotation updates: @Converter, @ForeignKey, @Index > > > --e89a8f234665dadbcc04d0803f0b-- From dev-return-21348-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 14:21:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9FF4AE1F2 for ; Mon, 10 Dec 2012 14:21:22 +0000 (UTC) Received: (qmail 50239 invoked by uid 500); 10 Dec 2012 14:21:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 50053 invoked by uid 500); 10 Dec 2012 14:21:21 -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 50016 invoked by uid 99); 10 Dec 2012 14:21:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 14:21:21 +0000 Date: Mon, 10 Dec 2012 14:21:21 +0000 (UTC) From: "Michael Glauche (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2303) second call of getSingleResult() fails with @EagerFetchMode(FetchMode.JOIN) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Michael Glauche created OPENJPA-2303: ---------------------------------------- Summary: second call of getSingleResult() fails with @EagerFetchMode(FetchMode.JOIN) Key: OPENJPA-2303 URL: https://issues.apache.org/jira/browse/OPENJPA-2303 Project: OpenJPA Issue Type: Bug Affects Versions: 2.2.1, 2.2.0 Reporter: Michael Glauche When an entity with a field like this: @OneToMany(mappedBy="parent", fetch=FetchType.EAGER) @EagerFetchMode(FetchMode.JOIN) is loaded with getSingleResult() for the second time, an Exception is thrown: javax.persistence.NonUniqueResultException: Query "select A from EntityA A where A.id=1" selected 3 results, but expected unique result. When i remove the @EagerFetchMode annotation everything works fine (but then n+1 selects are fired to load EntityA) See attached Test Project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21346-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 14:22:37 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BCEC8E20C for ; Mon, 10 Dec 2012 14:22:37 +0000 (UTC) Received: (qmail 31615 invoked by uid 500); 10 Dec 2012 14:15:56 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 31360 invoked by uid 500); 10 Dec 2012 14:15:51 -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 31290 invoked by uid 99); 10 Dec 2012 14:15:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 14:15:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 209.85.217.174 as permitted sender) Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 14:15:39 +0000 Received: by mail-lb0-f174.google.com with SMTP id gi11so2343273lbb.33 for ; Mon, 10 Dec 2012 06:15:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=uawRfGPtJW4ViD7A6CSFmj2CLmopZdfcfRm2ZR5B8+0=; b=ybILSH83wHessq/xCmxpntjcIJTlkvbTrDXXe5ZWBw0pv7HyWDJ1acbeVl85mTj6Fk HeC1sIUKXJRzhvg2IA2DORIdT2IXbR1slWg5bM+MxwqplooBZOlu1VZxPhKclrGLQHLF fiw7OaV7A8usWhWlXS7Ofa0485Z6rNyctdEMwXvZzuXt3Z1UYHA8oWtZacL8fOHdTRD7 rpINfa33+obCDC3ci5IgxabvdjadDEnSIlaooevcUX7ar9CdRuulYlHwOhQb1uG6XWyn L4GlO43XXB3LICDICrU0WMt6l5syxOGPVB7PAGserdjJ7uBIH9cWpmWb1S1yyfDBC7TS e7YQ== Received: by 10.152.104.240 with SMTP id gh16mr14179164lab.56.1355148919055; Mon, 10 Dec 2012 06:15:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.111.132 with HTTP; Mon, 10 Dec 2012 06:14:57 -0800 (PST) In-Reply-To: <1355105868.11180.YahooMailNeo@web124703.mail.ne1.yahoo.com> References: <1355105868.11180.YahooMailNeo@web124703.mail.ne1.yahoo.com> From: Kevin Sutter Date: Mon, 10 Dec 2012 08:14:57 -0600 Message-ID: Subject: Fwd: The bitter end of rsync-backed site management is coming Jan 1. To: users@openjpa.apache.org, dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=f46d04088e11f0256504d0803184 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04088e11f0256504d0803184 Content-Type: text/plain; charset=ISO-8859-1 Good morning, Don't worry... Even though OpenJPA is on the "naughty list" below, Joe is actively moving our website artifacts from Confluence to CMS per this JIRA: https://issues.apache.org/jira/browse/INFRA-5582. So, the coal will be replaced with candy very soon... :-) Kevin ---------- Forwarded message ---------- From: Joe Schaefer Date: Sun, Dec 9, 2012 at 8:17 PM Subject: The bitter end of rsync-backed site management is coming Jan 1. To: Apache Infrastructure NOTE: If your project's site is using the CMS or svnpubsub right now you may disregard this note. If you project is listed below, you have yet to migrate your site to either the CMS or svnpubsub, which becomes mandatory starting January 1. This note will serve as your FINAL reminder to start the process of filing a JIRA ticket with INFRA to request a migration to one of those two options prior to January 1, or face a hasty unannounced withdrawal of support for your website during the month of January upon processing of all remaining timely outstanding requests filed before Jan 1. Thanks for your diligence in this matter, further questions may be addressed to infrastructure@apache.org. SANTA'S NAUGHTY LIST: activemq.apache.org apr.apache.org archive.apache.org buildr.apache.org click.apache.org commons.apache.org db.apache.org directory.apache.org favicon.ico felix.apache.org forrest.apache.org geronimo.apache.org hadoop.apache.org hbase.apache.org hc.apache.org hive.apache.org jackrabbit.apache.org jmeter.apache.org juddi.apache.org karaf.apache.org lenya.apache.org maven.apache.org ode.apache.org openjpa.apache.org openwebbeans.apache.org perl.apache.org pig.apache.org poi.apache.org portals.apache.org roller.apache.org santuario.apache.org shiro.apache.org sling.apache.org spamassassin.apache.org struts.apache.org synapse.apache.org tapestry.apache.org tcl.apache.org tiles.apache.org turbine.apache.org tuscany.apache.org uima.apache.org velocity.apache.org whirr.apache.org wiki.apache.org ws.apache.org xerces.apache.org xml.apache.org xmlbeans.apache.org --f46d04088e11f0256504d0803184-- From dev-return-21349-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 14:23:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E5FD7E219 for ; Mon, 10 Dec 2012 14:23:21 +0000 (UTC) Received: (qmail 53768 invoked by uid 500); 10 Dec 2012 14:23:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 53736 invoked by uid 500); 10 Dec 2012 14:23:21 -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 53710 invoked by uid 99); 10 Dec 2012 14:23:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 14:23:21 +0000 Date: Mon, 10 Dec 2012 14:23:21 +0000 (UTC) From: "Michael Glauche (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2303) second call of getSingleResult() fails with @EagerFetchMode(FetchMode.JOIN) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glauche updated OPENJPA-2303: ------------------------------------- Attachment: jpaTest.zip Test project for the bug > second call of getSingleResult() fails with @EagerFetchMode(FetchMode.JOIN) > --------------------------------------------------------------------------- > > Key: OPENJPA-2303 > URL: https://issues.apache.org/jira/browse/OPENJPA-2303 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 2.2.0, 2.2.1 > Reporter: Michael Glauche > Attachments: jpaTest.zip > > > When an entity with a field like this: > @OneToMany(mappedBy="parent", fetch=FetchType.EAGER) > @EagerFetchMode(FetchMode.JOIN) > is loaded with getSingleResult() for the second time, an Exception is thrown: > javax.persistence.NonUniqueResultException: Query "select A from EntityA A where A.id=1" selected 3 results, but expected unique result. > When i remove the @EagerFetchMode annotation everything works fine (but then n+1 selects are fired to load EntityA) > See attached Test Project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21350-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon Dec 10 20:25:42 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9949CD803 for ; Mon, 10 Dec 2012 20:25:42 +0000 (UTC) Received: (qmail 81144 invoked by uid 500); 10 Dec 2012 20:25:42 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 81065 invoked by uid 500); 10 Dec 2012 20:25:42 -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 81048 invoked by uid 99); 10 Dec 2012 20:25:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 20:25:42 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 20:25:34 +0000 Received: by mail-la0-f46.google.com with SMTP id p5so2636473lag.33 for ; Mon, 10 Dec 2012 12:25:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=JcYzeSGz5gWtAgZMuhMS2wzidBtp4q1wiNekxS2FP2A=; b=XbnMIR2/RqplxUAWeA9Ro4GcO2YLoZgv7drs/M/6qMBdlkJSnGuOEJ1rePOloaabWo 9yrexYBiSwbSqbvEcHhyuTw3DwsyzYIZXuB/UOjMg2X1cekunvvBr3UOBt84YqCE4Giz OLcDFxF3UTqjZNkbQyR/nU8Ob++MYrC3sadgt0unM+8z3Xx+mLoOTLodn0hRRI7g5YRw Bhnykt2MpCoBr6K3WCkZVsalKzFV+9cKRrDiWG41kfbS+FG8Vg8a/57mCOdoIR3qKr+v MHlNacXa364BCnLQ0lXVhpE0b+BUy4ZHWPezAMu9r4IzCHVQh3DfREO44zzGvukubF0R PRVw== Received: by 10.112.28.9 with SMTP id x9mr6595356lbg.27.1355171113966; Mon, 10 Dec 2012 12:25:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.111.132 with HTTP; Mon, 10 Dec 2012 12:24:53 -0800 (PST) From: Kevin Sutter Date: Mon, 10 Dec 2012 14:24:53 -0600 Message-ID: Subject: New CMS OpenJPA web site is now live! To: users@openjpa.apache.org, dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=bcaec554dd00db9e8004d0855c90 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec554dd00db9e8004d0855c90 Content-Type: text/plain; charset=ISO-8859-1 The new CMS OpenJPA web site is now live: http://openjpa.apache.org/ You might have to reload/refresh the page to get the latest updates. For the most part, you shouldn't see any difference. There are some slight changes to formatting, images, etc. But, the content should be pretty much identical. Take a look around and let us know if there's something amiss. Thanks. If you need to make updates to the OpenJPA wiki, you'll need to follow the CMS update guidelines: http://www.apache.org/dev/cms.html#usage It's pretty straight forward. I just did a couple of minor updates as I was perusing the site. It's much easier to update the site than it was previous. Enjoy! Kevin --bcaec554dd00db9e8004d0855c90-- From dev-return-21351-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 10:01:40 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 68A8CD287 for ; Tue, 11 Dec 2012 10:01:40 +0000 (UTC) Received: (qmail 77360 invoked by uid 500); 11 Dec 2012 10:01:40 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 77098 invoked by uid 500); 11 Dec 2012 10:01:36 -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 77045 invoked by uid 99); 11 Dec 2012 10:01:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 10:01:34 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rmannibucau@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 10:01:29 +0000 Received: by mail-la0-f46.google.com with SMTP id p5so3150601lag.33 for ; Tue, 11 Dec 2012 02:01:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=xvbWRDT6fwg8nNBaKZ2owIzIDfDQ40bgD9X9LTXpXF0=; b=GRV9cqE4zPWGDaeoaDj/LnZyk7yBmluu0tZ7JMVKQTnFU1Lc6Vv6+RIGMity7dAAGl POXj2hbRZJZPXPwuaLDscGOSd6q0kGPHKThgX/D0BNoDJpaMS/eMc3ixj/cajqhzLjq9 Z8Dng5iFd6yowr75HqV8UH+HOsv+Km6wq7hkp/IS76MV2R88rdeuR4ksyvw+ssJCqcw5 bOlXh0j7hqRXGQYBjm6NlfyZEE5BiX33Qo7CVq8Rmxu+SSP/vOkiXJVJuwBNzer3nTT3 jv5UEzCZHRZiz7iOAqGD4ax8FtiYLpCMA5xxI/81mNWENLtnr2VOMR9WgeZQ3uhdRX3l p4lA== Received: by 10.112.42.197 with SMTP id q5mr7378624lbl.9.1355220067978; Tue, 11 Dec 2012 02:01:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.67.106 with HTTP; Tue, 11 Dec 2012 02:00:47 -0800 (PST) From: Romain Manni-Bucau Date: Tue, 11 Dec 2012 11:00:47 +0100 Message-ID: Subject: doc broken? To: dev@openjpa.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi guys, seems the doc is currently broken: http://openjpa.apache.org/documentation.html can't find any of these links known? normal? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau From dev-return-21352-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 14:20:51 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B00ED317 for ; Tue, 11 Dec 2012 14:20:51 +0000 (UTC) Received: (qmail 9923 invoked by uid 500); 11 Dec 2012 14:20:49 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 8411 invoked by uid 500); 11 Dec 2012 14:20:42 -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 8366 invoked by uid 99); 11 Dec 2012 14:20:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 14:20:40 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 209.85.161.174 as permitted sender) Received: from [209.85.161.174] (HELO mail-gg0-f174.google.com) (209.85.161.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 14:20:35 +0000 Received: by mail-gg0-f174.google.com with SMTP id k2so756328ggd.33 for ; Tue, 11 Dec 2012 06:20:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=gKTk3P7X0u0nufHWESJGZJvLLfqDNKZ/+Aiwsuat16E=; b=cCb352Aa2RDj46aiyq11+Tr5dxR+i3+7Dm1sj9u7wZXc/iEsv8TM0DBJdYxz3HXEq/ QhsIKRI1h5CLM2scrUkX32ZCSP7Wod4s0cz6YjYKAJHROXXaW2hm6oNfTIYfc1F0h+/U DtJvcdEgI+cfx3uxcpo3ofWr76xz+lFcSoYvTcPWseM4lYokaXyzSSKTKbeVhepIyi3J xO85Acxap0WL7ymzQYJIXvEhVPUJTu7lTLKbxwsOovi2QWTAqcKxWacE1YVP9mb8TgO9 LDrVubhADy/+BMgZZll5EZDwpejZTCcepICweBBoVS3pxAbHYKy3K9QMktBvTNlHl4AF EFDQ== Received: by 10.236.116.201 with SMTP id g49mr2017553yhh.73.1355235614241; Tue, 11 Dec 2012 06:20:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.147.181.8 with HTTP; Tue, 11 Dec 2012 06:19:53 -0800 (PST) In-Reply-To: References: From: Kevin Sutter Date: Tue, 11 Dec 2012 08:19:53 -0600 Message-ID: Subject: Re: doc broken? To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=20cf303bfae85fb22004d0946133 X-Virus-Checked: Checked by ClamAV on apache.org --20cf303bfae85fb22004d0946133 Content-Type: text/plain; charset=ISO-8859-1 Hi Romain, This looks to be related to the recent update for the CMS wiki... http://openjpa.208410.n2.nabble.com/New-CMS-OpenJPA-web-site-is-now-live-td7582124.html I'll check into this and reply back when it's resolved. Thanks for your patience. Kevin On Tue, Dec 11, 2012 at 4:00 AM, Romain Manni-Bucau wrote: > Hi guys, > > seems the doc is currently broken: > http://openjpa.apache.org/documentation.html > > can't find any of these links > > known? normal? > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > --20cf303bfae85fb22004d0946133-- From dev-return-21353-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 14:31:23 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 238B7D510 for ; Tue, 11 Dec 2012 14:31:23 +0000 (UTC) Received: (qmail 42969 invoked by uid 500); 11 Dec 2012 14:31:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 42915 invoked by uid 500); 11 Dec 2012 14:31:22 -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 42375 invoked by uid 99); 11 Dec 2012 14:31:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 14:31:22 +0000 Date: Tue, 11 Dec 2012 14:31:21 +0000 (UTC) From: "Pat McCabe (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-1979) Regression for non-standard joins with constant column values MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529006#comment-13529006 ] Pat McCabe commented on OPENJPA-1979: ------------------------------------- Hello. Is there any update on if/when this fix will be available ? > Regression for non-standard joins with constant column values > -------------------------------------------------------------- > > Key: OPENJPA-1979 > URL: https://issues.apache.org/jira/browse/OPENJPA-1979 > Project: OpenJPA > Issue Type: Bug > Components: jdbc, kernel > Affects Versions: 2.0.0-M1, 2.0.0 > Reporter: Pinaki Poddar > Attachments: OPENJPA-1979.patch.1.txt, Test-1979.zip > > > The non-standard join can use constant column values by enclosing them in single-quote character. This behavior is regressed. The likely cause of this regression is new delimiting support for schema elements introduced in JPA 2.0. The constant column value used to be detected during schema definition based on the assumption of the name being enclosed in single-quote. Due to introduction of delimiting capability, the constant value is now enclosed in double-quote followed by a single-quote. > The visible effect is failure to define schema for non-standard join with constant values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21354-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 15:39:28 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 404E8D9F0 for ; Tue, 11 Dec 2012 15:39:28 +0000 (UTC) Received: (qmail 3369 invoked by uid 500); 11 Dec 2012 15:39:24 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 2958 invoked by uid 500); 11 Dec 2012 15:39:24 -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 754 invoked by uid 99); 11 Dec 2012 15:39:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 15:39:21 +0000 Date: Tue, 11 Dec 2012 15:39:21 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2302) Slice support for QueryCompilationCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated OPENJPA-2302: ------------------------------------ Attachment: (was: patch.diff) > Slice support for QueryCompilationCache > --------------------------------------- > > Key: OPENJPA-2302 > URL: https://issues.apache.org/jira/browse/OPENJPA-2302 > Project: OpenJPA > Issue Type: Improvement > Components: slice > Affects Versions: 2.3.0, 2.2.1 > Reporter: fabio martelli > Fix For: 2.3.0 > > > It seems that slice doesn't support QueryCompilationCache. > By running the following test case ... > public class TestQueryCompilationCache extends SliceTestCase { > /** > * Specify persistence unit name as System property > * -Dunit or use the default value as > * "slice". > */ > protected String getPersistenceUnitName() { > return System.getProperty("unit", "slice"); > } > @Override > public void setUp() { > super.setUp(PObject.class, > "openjpa.QueryCompilationCache", "true"); > } > public void testQueryCompilationCache() > throws Exception { > OpenJPAEntityManager em = emf.createEntityManager(); > em.getTransaction().begin(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.getTransaction().commit(); > em.close(); > em = emf.createEntityManager(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.close(); > emf.close(); > } > } > The following exception will be raised. > testQueryCompilationCache(org.apache.openjpa.slice.TestQueryCompilationCache) Time elapsed: 1.923 sec <<< ERROR! > org.apache.openjpa.persistence.PersistenceException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$ParallelExecutor.executeQuery(DistributedStoreQuery.java:156) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794) > at org.apache.openjpa.slice.DistributedQueryImpl.execute(DistributedQueryImpl.java:61) > at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542) > at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286) > at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302) > at org.apache.openjpa.slice.TestQueryCompilationCache.testQueryCompilationCache(TestQueryCompilationCache.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at org.apache.openjpa.slice.PersistenceTestCase.run(PersistenceTestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: org.apache.openjpa.persistence.InvalidStateException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:4683) > at org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:1700) > at org.apache.openjpa.kernel.QueryImpl.isUnique(QueryImpl.java:453) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.calculateEagerMode(JDBCStoreQuery.java:483) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeQuery(JDBCStoreQuery.java:174) > at org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeQuery(ExpressionStoreQuery.java:783) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:273) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:266) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21355-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 15:41:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB9CCDA0E for ; Tue, 11 Dec 2012 15:41:22 +0000 (UTC) Received: (qmail 11335 invoked by uid 500); 11 Dec 2012 15:41:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 11171 invoked by uid 500); 11 Dec 2012 15:41:22 -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 11158 invoked by uid 99); 11 Dec 2012 15:41:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 15:41:22 +0000 Date: Tue, 11 Dec 2012 15:41:22 +0000 (UTC) From: "fabio martelli (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2302) Slice support for QueryCompilationCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated OPENJPA-2302: ------------------------------------ Attachment: patch.diff > Slice support for QueryCompilationCache > --------------------------------------- > > Key: OPENJPA-2302 > URL: https://issues.apache.org/jira/browse/OPENJPA-2302 > Project: OpenJPA > Issue Type: Improvement > Components: slice > Affects Versions: 2.3.0, 2.2.1 > Reporter: fabio martelli > Fix For: 2.3.0 > > Attachments: patch.diff > > > It seems that slice doesn't support QueryCompilationCache. > By running the following test case ... > public class TestQueryCompilationCache extends SliceTestCase { > /** > * Specify persistence unit name as System property > * -Dunit or use the default value as > * "slice". > */ > protected String getPersistenceUnitName() { > return System.getProperty("unit", "slice"); > } > @Override > public void setUp() { > super.setUp(PObject.class, > "openjpa.QueryCompilationCache", "true"); > } > public void testQueryCompilationCache() > throws Exception { > OpenJPAEntityManager em = emf.createEntityManager(); > em.getTransaction().begin(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.getTransaction().commit(); > em.close(); > em = emf.createEntityManager(); > em.createQuery("SELECT o from PObject o").getResultList(); > em.close(); > emf.close(); > } > } > The following exception will be raised. > testQueryCompilationCache(org.apache.openjpa.slice.TestQueryCompilationCache) Time elapsed: 1.923 sec <<< ERROR! > org.apache.openjpa.persistence.PersistenceException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$ParallelExecutor.executeQuery(DistributedStoreQuery.java:156) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794) > at org.apache.openjpa.slice.DistributedQueryImpl.execute(DistributedQueryImpl.java:61) > at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542) > at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286) > at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302) > at org.apache.openjpa.slice.TestQueryCompilationCache.testQueryCompilationCache(TestQueryCompilationCache.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at org.apache.openjpa.slice.PersistenceTestCase.run(PersistenceTestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: org.apache.openjpa.persistence.InvalidStateException: The context has been closed. The stack trace at which the context was closed is available if Runtime=TRACE logging is enabled. > at org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:4683) > at org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:1700) > at org.apache.openjpa.kernel.QueryImpl.isUnique(QueryImpl.java:453) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.calculateEagerMode(JDBCStoreQuery.java:483) > at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeQuery(JDBCStoreQuery.java:174) > at org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeQuery(ExpressionStoreQuery.java:783) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:273) > at org.apache.openjpa.slice.jdbc.DistributedStoreQuery$QueryExecutor.call(DistributedStoreQuery.java:266) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21356-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 18:15:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E52AAD3B4 for ; Tue, 11 Dec 2012 18:15:21 +0000 (UTC) Received: (qmail 71655 invoked by uid 500); 11 Dec 2012 18:15:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 71573 invoked by uid 500); 11 Dec 2012 18:15:21 -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 71433 invoked by uid 99); 11 Dec 2012 18:15:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 18:15:21 +0000 Date: Tue, 11 Dec 2012 18:15:21 +0000 (UTC) From: "Pinaki Poddar (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2304) Thread deadlock in CriteriaBuilder MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Pinaki Poddar created OPENJPA-2304: -------------------------------------- Summary: Thread deadlock in CriteriaBuilder Key: OPENJPA-2304 URL: https://issues.apache.org/jira/browse/OPENJPA-2304 Project: OpenJPA Issue Type: Bug Components: criteria Affects Versions: 2.2.1.1 Environment: Multi-core virtualized CPUs Reporter: Pinaki Poddar Assignee: Pinaki Poddar Fix For: 2.2.1.1 The CriteriaBuilder blocks when multiple threads work on constructing predicate expressions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21357-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 18:21:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7BEEAD3DC for ; Tue, 11 Dec 2012 18:21:22 +0000 (UTC) Received: (qmail 91113 invoked by uid 500); 11 Dec 2012 18:21:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 91037 invoked by uid 500); 11 Dec 2012 18:21:22 -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 90924 invoked by uid 99); 11 Dec 2012 18:21:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 18:21:21 +0000 Date: Tue, 11 Dec 2012 18:21:21 +0000 (UTC) From: "Pinaki Poddar (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Pinaki Poddar created OPENJPA-2305: -------------------------------------- Summary: Canonical MetaModel class generation should not use inhertence Key: OPENJPA-2305 URL: https://issues.apache.org/jira/browse/OPENJPA-2305 Project: OpenJPA Issue Type: Bug Components: criteria Affects Versions: 2.2.1.1 Reporter: Pinaki Poddar Assignee: Pinaki Poddar Fix For: 2.2.1.1 The generated source code for canonical metamodel classes mirrored the same inheritance hierarchy of the domain classes. This strategy exposed an error that resulted in wrong target SQL query under the following domain model a) A @MappedSuperClass M defined a primary key field x b) The primary key field x is an @EmbeddedId E c) An @Entity class D derived from M and navigated to the fields of E via x The solution is to generate canonical class D_.java as a flattened structure instead of inheriting from M_.java (as is done currently). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21358-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:31:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 892B4DEFC for ; Tue, 11 Dec 2012 20:31:21 +0000 (UTC) Received: (qmail 53548 invoked by uid 500); 11 Dec 2012 20:31:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 53512 invoked by uid 500); 11 Dec 2012 20:31:21 -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 53501 invoked by uid 99); 11 Dec 2012 20:31:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:31:21 +0000 Date: Tue, 11 Dec 2012 20:31:20 +0000 (UTC) From: "Sebb (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2306) Broken link MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sebb created OPENJPA-2306: ----------------------------- Summary: Broken link Key: OPENJPA-2306 URL: https://issues.apache.org/jira/browse/OPENJPA-2306 Project: OpenJPA Issue Type: Bug Components: docs Environment: http://openjpa.apache.org/downloads.html Reporter: Sebb Priority: Minor http://openjpa.apache.org/downloads.html#verifying-releases.html should be http://openjpa.apache.org/downloads.html#verifying-releases -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21359-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:35:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7FEB4DF30 for ; Tue, 11 Dec 2012 20:35:22 +0000 (UTC) Received: (qmail 68552 invoked by uid 500); 11 Dec 2012 20:35:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 68483 invoked by uid 500); 11 Dec 2012 20:35:22 -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 68391 invoked by uid 99); 11 Dec 2012 20:35:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:35:22 +0000 Date: Tue, 11 Dec 2012 20:35:22 +0000 (UTC) From: "Sebb (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sebb created OPENJPA-2307: ----------------------------- Summary: Download page must not advertise snapshot builds Key: OPENJPA-2307 URL: https://issues.apache.org/jira/browse/OPENJPA-2307 Project: OpenJPA Issue Type: Bug Reporter: Sebb Priority: Critical The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21360-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:47:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 55077DF87 for ; Tue, 11 Dec 2012 20:47:22 +0000 (UTC) Received: (qmail 7690 invoked by uid 500); 11 Dec 2012 20:47:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 7630 invoked by uid 500); 11 Dec 2012 20:47:22 -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 7583 invoked by uid 99); 11 Dec 2012 20:47:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:47:22 +0000 Date: Tue, 11 Dec 2012 20:47:22 +0000 (UTC) From: "Sebb (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2308) Remove superseded releases from main Apache mirrors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sebb created OPENJPA-2308: ----------------------------- Summary: Remove superseded releases from main Apache mirrors Key: OPENJPA-2308 URL: https://issues.apache.org/jira/browse/OPENJPA-2308 Project: OpenJPA Issue Type: Bug Components: build / infrastructure Affects Versions: 2.2.0, 2.1.1, 2.1.0 Reporter: Sebb Only the current release should appear on the ASF mirrors. This is to reduce the disk space requirements for the mirror system. It takes a few days for all mirrors to catch up with a new release, but after a suitable period (e.g. a week) any superseded releasese should be deleted from: http://www.apache.org/dist/openjpa/ In some cases, projects maintain several release series (e.g. Tomcat6 and Tomcat7) in which case only the latest of each series should remain on the mirror system. AFAICT, the following releases are no longer current and should be removed: 2.1.0 2.1.1 2.2.0 Older releases are always available from archive.apache.org. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21361-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:47:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 97CD9DF8A for ; Tue, 11 Dec 2012 20:47:22 +0000 (UTC) Received: (qmail 7870 invoked by uid 500); 11 Dec 2012 20:47:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 7837 invoked by uid 500); 11 Dec 2012 20:47:22 -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 7828 invoked by uid 99); 11 Dec 2012 20:47:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:47:22 +0000 Date: Tue, 11 Dec 2012 20:47:22 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529325#comment-13529325 ] Kevin Sutter commented on OPENJPA-2307: --------------------------------------- The download links on this page are clearly separated based on Releases vs Nightly Snapshots. The official releases are at the top of this page, and the nightly snapshots at the bottom of this page. The nightly snapshot section clearly has this text: Nightly Snapshots These distributions are built and deployed nightly, and contain up-to-date fixes and improvements. However, their stability cannot be guaranteed. Use at your own risk. The OpenJPA site has been formatted this way forever. Although this JIRA is a nice suggestion, I don't see it as a bug that needs to be resolved. Unless you are indicating that we're breaking some type of Apache rule, I don't see any reason to separate these downloads into separate pages. > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21362-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:47:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B9B56DF8B for ; Tue, 11 Dec 2012 20:47:22 +0000 (UTC) Received: (qmail 8019 invoked by uid 500); 11 Dec 2012 20:47:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 7975 invoked by uid 500); 11 Dec 2012 20:47:22 -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 7897 invoked by uid 99); 11 Dec 2012 20:47:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:47:22 +0000 Date: Tue, 11 Dec 2012 20:47:22 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter resolved OPENJPA-2307. ----------------------------------- Resolution: Won't Fix Assignee: Kevin Sutter > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21363-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:51:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D405DFB3 for ; Tue, 11 Dec 2012 20:51:21 +0000 (UTC) Received: (qmail 25165 invoked by uid 500); 11 Dec 2012 20:51:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 25128 invoked by uid 500); 11 Dec 2012 20:51:21 -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 25113 invoked by uid 99); 11 Dec 2012 20:51:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:51:21 +0000 Date: Tue, 11 Dec 2012 20:51:20 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (OPENJPA-2306) Broken link MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter resolved OPENJPA-2306. ----------------------------------- Resolution: Fixed Assignee: Kevin Sutter Done. Thanks for the catch. > Broken link > ----------- > > Key: OPENJPA-2306 > URL: https://issues.apache.org/jira/browse/OPENJPA-2306 > Project: OpenJPA > Issue Type: Bug > Components: docs > Environment: http://openjpa.apache.org/downloads.html > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Minor > > http://openjpa.apache.org/downloads.html#verifying-releases.html > should be > http://openjpa.apache.org/downloads.html#verifying-releases -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21364-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 20:51:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BCCCFDFB5 for ; Tue, 11 Dec 2012 20:51:21 +0000 (UTC) Received: (qmail 25437 invoked by uid 500); 11 Dec 2012 20:51:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 25323 invoked by uid 500); 11 Dec 2012 20:51:21 -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 25314 invoked by uid 99); 11 Dec 2012 20:51:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 20:51:21 +0000 Date: Tue, 11 Dec 2012 20:51:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (OPENJPA-2306) Broken link MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter closed OPENJPA-2306. --------------------------------- > Broken link > ----------- > > Key: OPENJPA-2306 > URL: https://issues.apache.org/jira/browse/OPENJPA-2306 > Project: OpenJPA > Issue Type: Bug > Components: docs > Environment: http://openjpa.apache.org/downloads.html > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Minor > > http://openjpa.apache.org/downloads.html#verifying-releases.html > should be > http://openjpa.apache.org/downloads.html#verifying-releases -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21365-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:01:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A19BCD10A for ; Tue, 11 Dec 2012 21:01:22 +0000 (UTC) Received: (qmail 69034 invoked by uid 500); 11 Dec 2012 21:01:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 69003 invoked by uid 500); 11 Dec 2012 21:01:22 -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 68991 invoked by uid 99); 11 Dec 2012 21:01:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:01:22 +0000 Date: Tue, 11 Dec 2012 21:01:20 +0000 (UTC) From: "Sebb (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened OPENJPA-2307: --------------------------- I'm sorry, but snapshot builds must not be advertised to the general public. http://www.apache.org/dev/release.html#what > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21366-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:03:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F33BDD11D for ; Tue, 11 Dec 2012 21:03:21 +0000 (UTC) Received: (qmail 75042 invoked by uid 500); 11 Dec 2012 21:03:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 74964 invoked by uid 500); 11 Dec 2012 21:03:21 -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 74809 invoked by uid 99); 11 Dec 2012 21:03:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:03:21 +0000 Date: Tue, 11 Dec 2012 21:03:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529333#comment-13529333 ] Kevin Sutter commented on OPENJPA-2307: --------------------------------------- Bummer... :-) Looks to be a valid defect... > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21367-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:37:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 83F3BD440 for ; Tue, 11 Dec 2012 21:37:21 +0000 (UTC) Received: (qmail 77880 invoked by uid 500); 11 Dec 2012 21:37:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 77835 invoked by uid 500); 11 Dec 2012 21:37:21 -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 77826 invoked by uid 99); 11 Dec 2012 21:37:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:37:21 +0000 Date: Tue, 11 Dec 2012 21:37:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2308) Remove superseded releases from main Apache mirrors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529359#comment-13529359 ] Kevin Sutter commented on OPENJPA-2308: --------------------------------------- Thanks for the catch. I've updated the links on the download page to point at the archive site and I have deleted the old directories from the http://www.apache.org/dist/openjpa/. > Remove superseded releases from main Apache mirrors > --------------------------------------------------- > > Key: OPENJPA-2308 > URL: https://issues.apache.org/jira/browse/OPENJPA-2308 > Project: OpenJPA > Issue Type: Bug > Components: build / infrastructure > Affects Versions: 2.1.0, 2.1.1, 2.2.0 > Reporter: Sebb > > Only the current release should appear on the ASF mirrors. > This is to reduce the disk space requirements for the mirror system. > It takes a few days for all mirrors to catch up with a new release, but after a suitable period (e.g. a week) any superseded releasese should be deleted from: > http://www.apache.org/dist/openjpa/ > In some cases, projects maintain several release series (e.g. Tomcat6 and Tomcat7) in which case only the latest of each series should remain on the mirror system. > AFAICT, the following releases are no longer current and should be removed: > 2.1.0 > 2.1.1 > 2.2.0 > Older releases are always available from archive.apache.org. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21368-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:37:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 56450D445 for ; Tue, 11 Dec 2012 21:37:22 +0000 (UTC) Received: (qmail 78443 invoked by uid 500); 11 Dec 2012 21:37:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 78400 invoked by uid 500); 11 Dec 2012 21:37:22 -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 78310 invoked by uid 99); 11 Dec 2012 21:37:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:37:21 +0000 Date: Tue, 11 Dec 2012 21:37:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (OPENJPA-2308) Remove superseded releases from main Apache mirrors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter resolved OPENJPA-2308. ----------------------------------- Resolution: Fixed Assignee: Kevin Sutter > Remove superseded releases from main Apache mirrors > --------------------------------------------------- > > Key: OPENJPA-2308 > URL: https://issues.apache.org/jira/browse/OPENJPA-2308 > Project: OpenJPA > Issue Type: Bug > Components: build / infrastructure > Affects Versions: 2.1.0, 2.1.1, 2.2.0 > Reporter: Sebb > Assignee: Kevin Sutter > > Only the current release should appear on the ASF mirrors. > This is to reduce the disk space requirements for the mirror system. > It takes a few days for all mirrors to catch up with a new release, but after a suitable period (e.g. a week) any superseded releasese should be deleted from: > http://www.apache.org/dist/openjpa/ > In some cases, projects maintain several release series (e.g. Tomcat6 and Tomcat7) in which case only the latest of each series should remain on the mirror system. > AFAICT, the following releases are no longer current and should be removed: > 2.1.0 > 2.1.1 > 2.2.0 > Older releases are always available from archive.apache.org. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21369-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:47:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 608C3D4B0 for ; Tue, 11 Dec 2012 21:47:21 +0000 (UTC) Received: (qmail 11663 invoked by uid 500); 11 Dec 2012 21:47:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 11613 invoked by uid 500); 11 Dec 2012 21:47:21 -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 11603 invoked by uid 99); 11 Dec 2012 21:47:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:47:21 +0000 Date: Tue, 11 Dec 2012 21:47:20 +0000 (UTC) From: "Sebb (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (OPENJPA-2308) Remove superseded releases from main Apache mirrors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed OPENJPA-2308. ------------------------- Thanks. > Remove superseded releases from main Apache mirrors > --------------------------------------------------- > > Key: OPENJPA-2308 > URL: https://issues.apache.org/jira/browse/OPENJPA-2308 > Project: OpenJPA > Issue Type: Bug > Components: build / infrastructure > Affects Versions: 2.1.0, 2.1.1, 2.2.0 > Reporter: Sebb > Assignee: Kevin Sutter > > Only the current release should appear on the ASF mirrors. > This is to reduce the disk space requirements for the mirror system. > It takes a few days for all mirrors to catch up with a new release, but after a suitable period (e.g. a week) any superseded releasese should be deleted from: > http://www.apache.org/dist/openjpa/ > In some cases, projects maintain several release series (e.g. Tomcat6 and Tomcat7) in which case only the latest of each series should remain on the mirror system. > AFAICT, the following releases are no longer current and should be removed: > 2.1.0 > 2.1.1 > 2.2.0 > Older releases are always available from archive.apache.org. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21370-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:51:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C1BA2D4F1 for ; Tue, 11 Dec 2012 21:51:21 +0000 (UTC) Received: (qmail 29030 invoked by uid 500); 11 Dec 2012 21:51:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 28860 invoked by uid 500); 11 Dec 2012 21:51:21 -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 28851 invoked by uid 99); 11 Dec 2012 21:51:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:51:21 +0000 Date: Tue, 11 Dec 2012 21:51:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529374#comment-13529374 ] Kevin Sutter commented on OPENJPA-2307: --------------------------------------- As I was fixing OPENJPA-2308, I also discovered that the RELEASE-NOTES.html links are not valid on the Download page due to the lack of the "builds" directory on the openjpa.apache.org site... We'll have to get that fixed once we figure out the proper location for the Documentation... > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21371-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 21:57:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7B1F2D549 for ; Tue, 11 Dec 2012 21:57:21 +0000 (UTC) Received: (qmail 55567 invoked by uid 500); 11 Dec 2012 21:57:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 55543 invoked by uid 500); 11 Dec 2012 21:57:21 -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 55504 invoked by uid 99); 11 Dec 2012 21:57:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 21:57:21 +0000 Date: Tue, 11 Dec 2012 21:57:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529382#comment-13529382 ] Kevin Sutter commented on OPENJPA-2307: --------------------------------------- Can the main download page have a reference to the "developer only" page for the nightly snapshots? Or, does it have to be a standalone page with no link or mention of the development downloads? I'm assuming at a minimum, I could reference our general Development page and let developers go down that path... > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21372-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Dec 11 22:23:22 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0B970D6CC for ; Tue, 11 Dec 2012 22:23:22 +0000 (UTC) Received: (qmail 34256 invoked by uid 500); 11 Dec 2012 22:23:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 34205 invoked by uid 500); 11 Dec 2012 22:23:21 -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 34195 invoked by uid 99); 11 Dec 2012 22:23:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 22:23:21 +0000 Date: Tue, 11 Dec 2012 22:23:21 +0000 (UTC) From: "Sebb (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2307) Download page must not advertise snapshot builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529397#comment-13529397 ] Sebb commented on OPENJPA-2307: ------------------------------- I don't think the main download page should mention snapshot builds even indirectly. It would be better to add the nightly build reference somewhere under the pages in the "Development" section of the navigation. For example it could be added to http://openjpa.apache.org/building.html > Download page must not advertise snapshot builds > ------------------------------------------------ > > Key: OPENJPA-2307 > URL: https://issues.apache.org/jira/browse/OPENJPA-2307 > Project: OpenJPA > Issue Type: Bug > Reporter: Sebb > Assignee: Kevin Sutter > Priority: Critical > > The download page http://openjpa.apache.org/downloads.html contains links to several snapshot builds. > These presumably have not been voted on; as such they are not proper ASF releases and must not be advertised to the general public. > They are only intended for use by developers and should only appear (if at all) in pages which are clearly for developers only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21373-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 12 16:51:30 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 564F0DE4A for ; Wed, 12 Dec 2012 16:51:30 +0000 (UTC) Received: (qmail 18605 invoked by uid 500); 12 Dec 2012 16:51:29 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 13757 invoked by uid 500); 12 Dec 2012 16:51: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 13645 invoked by uid 99); 12 Dec 2012 16:51:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2012 16:51:21 +0000 Date: Wed, 12 Dec 2012 16:51:20 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2309) Doc links are broken MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Kevin Sutter created OPENJPA-2309: ------------------------------------- Summary: Doc links are broken Key: OPENJPA-2309 URL: https://issues.apache.org/jira/browse/OPENJPA-2309 Project: OpenJPA Issue Type: Sub-task Components: docs Reporter: Kevin Sutter Assignee: Kevin Sutter Since we're addressing other wiki concerns via defects and I don't want anybody else to be wasting time figuring out the solution, I'm creating this defect to show that I am working the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21374-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 12 16:53:27 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BEED2DE76 for ; Wed, 12 Dec 2012 16:53:27 +0000 (UTC) Received: (qmail 24660 invoked by uid 500); 12 Dec 2012 16:53:27 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 22962 invoked by uid 500); 12 Dec 2012 16:53: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 22895 invoked by uid 99); 12 Dec 2012 16:53:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2012 16:53:22 +0000 Date: Wed, 12 Dec 2012 16:53:21 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2309) Doc links are broken MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter updated OPENJPA-2309: ---------------------------------- Description: Since we're addressing other wiki concerns via defects and I don't want anybody else to be wasting time figuring out the solution, I'm creating this defect to show that I am working the problem. All of the documentation links are broken from our wiki: http://openjpa.apache.org/documentation.html Also, the RELEASE-NOTES.html links on our download page are broken: http://openjpa.apache.org/downloads.html I have also searched out wiki pages and there are a few other references to our documentation that will need to be cleaned up. I am working with the Apache Infra team to figure out a new location to store our documentation and fix up the links. was:Since we're addressing other wiki concerns via defects and I don't want anybody else to be wasting time figuring out the solution, I'm creating this defect to show that I am working the problem. > Doc links are broken > -------------------- > > Key: OPENJPA-2309 > URL: https://issues.apache.org/jira/browse/OPENJPA-2309 > Project: OpenJPA > Issue Type: Sub-task > Components: docs > Reporter: Kevin Sutter > Assignee: Kevin Sutter > > Since we're addressing other wiki concerns via defects and I don't want anybody else to be wasting time figuring out the solution, I'm creating this defect to show that I am working the problem. > All of the documentation links are broken from our wiki: http://openjpa.apache.org/documentation.html > Also, the RELEASE-NOTES.html links on our download page are broken: http://openjpa.apache.org/downloads.html > I have also searched out wiki pages and there are a few other references to our documentation that will need to be cleaned up. I am working with the Apache Infra team to figure out a new location to store our documentation and fix up the links. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21375-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Dec 13 07:49:30 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04B3AD771 for ; Thu, 13 Dec 2012 07:49:29 +0000 (UTC) Received: (qmail 91247 invoked by uid 500); 13 Dec 2012 07:49:29 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 91000 invoked by uid 500); 13 Dec 2012 07: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 90936 invoked by uid 99); 13 Dec 2012 07:49:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 07:49:21 +0000 Date: Thu, 13 Dec 2012 07:49:21 +0000 (UTC) From: "victor chiong (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2310) find() method could not retrieve values from MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 victor chiong created OPENJPA-2310: -------------------------------------- Summary: find() method could not retrieve values from Key: OPENJPA-2310 URL: https://issues.apache.org/jira/browse/OPENJPA-2310 Project: OpenJPA Issue Type: Bug Components: jdbc, jpa Affects Versions: 2.2.0 Environment: TomCat 7.2,Netbeans 7.2.1, Windows 8 os. Reporter: victor chiong Priority: Blocker Fix For: 2.2.0 Why do find() don't poplate my entity? Base on the debug, it does not place any values to my entity. Please see link below. Thanks. Primary key as Strings will not work on find()? http://stackoverflow.com/questions/13835538/open-jpa-find-could-not-retrieve-the-value-of-the-entity-from-my-database -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From dev-return-21376-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Dec 13 13:32:21 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6FA9FDF9D for ; Thu, 13 Dec 2012 13:32:21 +0000 (UTC) Received: (qmail 97851 invoked by uid 500); 13 Dec 2012 13:32:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 97647 invoked by uid 500); 13 Dec 2012 13:32:15 -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 97233 invoked by uid 99); 13 Dec 2012 13:32:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 13:32:12 +0000 Date: Thu, 13 Dec 2012 13:32:12 +0000 (UTC) From: "Rick Curtis (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2310) find() method could not retrieve values from MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531006#comment-13531006 ] Rick Curtis commented on OPENJPA-2310: -------------------------------------- How are you enhancing your Entities? Please post the contents of your persistence.xml file. > find() method could not retrieve values from > --------------------------------------------- > > Key: OPENJPA-2310 > URL: https://issues.apache.org/jira/browse/OPENJPA-2310 > Project: OpenJPA > Issue Type: Bug > Components: jdbc, jpa > Affects Versions: 2.2.0 > Environment: TomCat 7.2,Netbeans 7.2.1, Windows 8 os. > Reporter: victor chiong > Priority: Blocker > Labels: newbie > Fix For: 2.2.0 > > > Why do find() don't poplate my entity? Base on the debug, it does not place any values to my entity. Please see link below. Thanks. Primary key as Strings will not work on find()? > http://stackoverflow.com/questions/13835538/open-jpa-find-could-not-retrieve-the-value-of-the-entity-from-my-database -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira