Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 33205 invoked from network); 19 Sep 2007 02:11:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Sep 2007 02:11:56 -0000 Received: (qmail 87916 invoked by uid 500); 19 Sep 2007 02:11:47 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 87886 invoked by uid 500); 19 Sep 2007 02:11:47 -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 87877 invoked by uid 99); 19 Sep 2007 02:11:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 19:11:47 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ppoddar@bea.com designates 66.248.192.39 as permitted sender) Received: from [66.248.192.39] (HELO repmmg02.bea.com) (66.248.192.39) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 02:13:43 +0000 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id l8J2BOM6031018 for ; Tue, 18 Sep 2007 19:11:24 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id l8J2BMfn004382 for ; Tue, 18 Sep 2007 19:11:23 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE: [jira] Commented: (OPENJPA-305) Dynamic configuration of EntityManagerFactory Date: Tue, 18 Sep 2007 19:08:54 -0700 Message-ID: <3992B07C0590B548BB294D31768A1DA2774318@repbex01.amer.bea.com> In-Reply-To: <31705630.1190167363662.JavaMail.jira@brutus> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [jira] Commented: (OPENJPA-305) Dynamic configuration of EntityManagerFactory Thread-Index: Acf6YTxXy6F5jwUVScSy5KxL/XzI3gAALxVA References: <15516536.1186084432901.JavaMail.jira@brutus> <31705630.1190167363662.JavaMail.jira@brutus> From: "Pinaki Poddar" To: x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Virus-Checked: Checked by ClamAV on apache.org >I don't understand why we do the isDynamic() check in equals() >and hashCode(), though; shouldn't getOriginalValue() always be correct? Correct. Thanks. Pinaki Poddar 972.834.2865 >-----Original Message----- >From: Patrick Linskey (JIRA) [mailto:jira@apache.org] >Sent: Tuesday, September 18, 2007 9:03 PM >To: dev@openjpa.apache.org >Subject: [jira] Commented: (OPENJPA-305) Dynamic configuration >of EntityManagerFactory > > > [ >https://issues.apache.org/jira/browse/OPENJPA-305?page=com.atla >ssian.jira.plugin.system.issuetabpanels:comment-tabpanel#action >_12528633 ] > >Patrick Linskey commented on OPENJPA-305: >----------------------------------------- > >Generally, it looks good. Some comments: > >I don't understand why we do the isDynamic() check in equals() >and hashCode(), though; shouldn't getOriginalValue() always be correct? > >Also, it looks like there's a synchronization issue at hand -- >based on my reading, dynamic sets must occur in a synchronized >manner, or the behavior is non-deterministic. That is OK (I >don't think that we necessarily want to add synchronization on >accesses), but should be well-documented. > >> Dynamic configuration of EntityManagerFactory >> --------------------------------------------- >> >> Key: OPENJPA-305 >> URL: >https://issues.apache.org/jira/browse/OPENJPA-305 >> Project: OpenJPA >> Issue Type: New Feature >> Reporter: Pinaki Poddar >> Attachments: openjpa-305.patch.1.txt >> >> >> OpenJPA configures EntityManagerFactory at creation time via >an instance of Configuartion object. Once EntityManagerFactory >is created and a EntityManager is issued from it -- the >Configuration is frozen by design. That is no further changes >to Configuration is allowed as long as EntityManagerFactory lives. >> For certain configuration properties, it is desirable to >change them during the lifetime of a EntityManagerFactory. >> This issue is raised to initiate a discussion on such a >feature, the possibility and limitations of dynamic update and >track the impact of such a change as frozen Configuration is >an important assumption. >> > >-- >This message is automatically generated by JIRA. >- >You can reply to this email to add a comment to the issue online. > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.