Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 94066 invoked from network); 19 Nov 2008 08:23:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Nov 2008 08:23:42 -0000 Received: (qmail 72471 invoked by uid 500); 19 Nov 2008 08:23:50 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 72449 invoked by uid 500); 19 Nov 2008 08: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 72438 invoked by uid 99); 19 Nov 2008 08:23:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Nov 2008 00:23:50 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists+1214986235816-210739@n2.nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Nov 2008 08:22:27 +0000 Received: from tervel.nabble.com ([192.168.236.150]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1L2iL9-0001cJ-CW for dev@openjpa.apache.org; Wed, 19 Nov 2008 00:23:11 -0800 Message-ID: <1227082991382-1518264.post@n2.nabble.com> Date: Wed, 19 Nov 2008 00:23:11 -0800 (PST) From: Pinaki Poddar To: dev@openjpa.apache.org Subject: Re: Extend Mapping classes or implement custom strategies? In-Reply-To: <1227075711921-1518056.post@n2.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ppoddar@apache.org References: <1227075711921-1518056.post@n2.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, An analogous usage is VersionStrategy. May be you should also refer to Custom Field Mapping [1] Adding extra temporal data to every instance is most likely can be accomplished by adding extra field mapping to an annotated class. So effectively the annotation should result in adding extra field mapping to ClassMapping. Then the user need not to declare fields for the temporal state. [1] http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_mapping_custom_field -- View this message in context: http://n2.nabble.com/Extend-Mapping-classes-or-implement-custom-strategies--tp1518056p1518264.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.