Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 95619 invoked from network); 28 Aug 2007 16:23:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Aug 2007 16:23:40 -0000 Received: (qmail 23553 invoked by uid 500); 28 Aug 2007 16:23:35 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 23401 invoked by uid 500); 28 Aug 2007 16:23:35 -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 23392 invoked by uid 99); 28 Aug 2007 16:23:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 09:23:35 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of plinskey@gmail.com designates 64.233.184.236 as permitted sender) Received: from [64.233.184.236] (HELO wr-out-0506.google.com) (64.233.184.236) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 16:23:30 +0000 Received: by wr-out-0506.google.com with SMTP id l58so1249064wrl for ; Tue, 28 Aug 2007 09:23:09 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ekCwhgR7sqc7n65azFvnKg85b0swjpx65D/svDhLK2jYjPbZDdT4hERC1Gr/WLQTylTpAu/M4+A6uvubuSdj0ClyhmgwgxS10RuhMgiCBFWTj8C17dU19a9kt+Uoj8TA20Kty/1DT3vAI+jmLiMm3FHBF9KTi+GB9mVDsUWQAWE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lcFL4/V5IBIBl25knqqQCbAAt1+cRi1a+Lc8P1Uqx7QrL/yDUrcRZIruKAHuvkS6g4i4jZmIqF3fppG0jvYvvfF9HNkIyQtaW53NsTK9iFmmYuscC5xWxeZUykxL9QndCxXUH1tx1zTVKlxrChz+5M7niMJtTSOfaWr/SMmg2M0= Received: by 10.90.105.20 with SMTP id d20mr889092agc.1188318189111; Tue, 28 Aug 2007 09:23:09 -0700 (PDT) Received: by 10.35.100.9 with HTTP; Tue, 28 Aug 2007 09:23:08 -0700 (PDT) Message-ID: <7262f25e0708280923v44b85630u27410b8b67fb83ea@mail.gmail.com> Date: Tue, 28 Aug 2007 09:23:08 -0700 From: "Patrick Linskey" To: dev@openjpa.apache.org Subject: Re: Implementing Temporal Property (or Temporal Object) using JPA? In-Reply-To: <08CB41C0-7A71-4A6A-95F4-4CEE7993AB1E@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5e15af530708280107p52d10607l8755ab7873d969ec@mail.gmail.com> <08CB41C0-7A71-4A6A-95F4-4CEE7993AB1E@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Paul, Marc's response is relative to implementing temporal features within OpenJPA. I have seen a number of people implement a model with temporal aspects on top of OpenJPA, using transaction listeners to update temporal data at appropriate times. What features in particular are you looking for? -Patrick On 8/28/07, Marc Prud'hommeaux wrote: > Paul- > > Support for temporal/auditing data has been often discussed in the > past, but no one has ever implemented. IMO, it would be a great > feature to have, and I believe that OpenJPA's architecture is > flexible enough to allow the implementation to be done largely in > isolation. > > All we would need is for someone to volunteer... > > > On Aug 28, 2007, at 4:07 AM, Hurragutt wrote: > > > Hi. > > Have anyone tried to implement Martin Fowlers Temporal Property > > (http://www.martinfowler.com/eaaDev/TemporalProperty.html) pattern > > using JPA? > > > > Or Temporal Object (http://www.martinfowler.com/eaaDev/ > > TemporalObject.html > > )? > > > > Sincerely, > > Paul Nyheim > > -- Patrick Linskey 202 669 5907