Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 32778 invoked from network); 5 Nov 2009 17:13:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Nov 2009 17:13:43 -0000 Received: (qmail 60844 invoked by uid 500); 5 Nov 2009 17:13:43 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 60774 invoked by uid 500); 5 Nov 2009 17:13: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 60764 invoked by uid 99); 5 Nov 2009 17:13:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 17:13:42 +0000 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: local policy) Received: from [216.252.110.63] (HELO web55902.mail.re3.yahoo.com) (216.252.110.63) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 05 Nov 2009 17:13:31 +0000 Received: (qmail 62085 invoked by uid 60001); 5 Nov 2009 17:13:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1257441190; bh=sLZG3xWySsE79wMfGuSR+RJI8udRYWV2I+P+L4VyEFU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=iSgc+6MjDAf4zDJu84yfcUft6YSrmjWhbcaeyCtAlhIzJa0IH9ml7Iv8/S7IgqyhDrVuV6pRwDe9idb5ifFWxzzhB9Y3jZs9dwkJ5eB5qYKljULiJIQoMJPYcOt1P5p5mhcpXBRDMxI3yIcjSzGPoFOTE7Hl3Q0q4mo/kl57b+Q= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nGzKqrKY6rUUEZWw5uuhxN/oAmLLyVcbQ/qFgiF9q0ZJPkyt0Tyd1+abmeP9qe6yd1zc7F6eujDGMyu0gnbXXrF0+gIfm5XdXDD2U7TVmqcbhqTlJPwz+tvPks/QO4LYikf4r/qMTE9cy3K4Hg/RFbudmpMRmvIluS2+5grn8ZI=; Message-ID: <358596.58982.qm@web55902.mail.re3.yahoo.com> X-YMail-OSG: dww4u2wVM1meFw.EE.b8TnQD82830D2HLLUjXZkhZpMnZDrLlirynnWpLax6vqP0AjOiqxs7eBJleALSUZtSXW_cB99NljqC4QSmni_nd_uX7mn98uF6Te3Dwgv5nDS8x0zfo.yaiFMuSInjMSbDLMr9YBOpH1edSRohFlkRuBUJ7Zadn3ByAMyWSRqJEwmQAfg2vFMfD2kDjbuooWDu0uHdEsa1PTqDmbYm4gB720c4gSAiAOlDg4unb9wJWPx4HZ_eJ0iz8M8LdCOjRHhFgsp0s7LJXUsBlW4vAidLbYUVNwhrG8Qh__9_qdmbdWP_D7NuRnPT0hEdV6VJZj49vk86wu9KOA49JqbtE.VPdEdgmQ73TQ39xqd.yu2YTRn8A3TCj8wei.RzRz3V0XZIepW1ARMc.W1PZwHoldOul3FVHWu2F9_THF.iXrUBTZQrHedTPAza3BoLEfa7K1NxoiV4POJ9.Ko2BSbxUe8jfARqW2x_lblOusxT_0Ut._ZkqrtK7M6hDo.MebRtETZAKW1Lqvh1ZyOgXPZiaaGta7ZUc6T2PpLLonPyWjeFa5XX65CNAGX0YJS8.6JtvApUDGMKP4_yClVurj4WW.xBp7br46EtFT.oeqIhTFa3lMxNshnDVHTP661pgJ9ECumvM1V4NpVCvhv_Jq1bUTq341t3bkJZtwZJyWc_MDTIuh1_m2e5XCsnq6E8jty3xhwP3W1vZfdk_AusTSRg2rpDqZY- Received: from [216.101.109.137] by web55902.mail.re3.yahoo.com via HTTP; Thu, 05 Nov 2009 09:13:10 PST X-Mailer: YahooMailRC/211.6 YahooMailWebService/0.7.361.4 References: <1257408405153-3950794.post@n2.nabble.com> Date: Thu, 5 Nov 2009 09:13:10 -0800 (PST) From: Fay Wang Subject: Re: version field dont work when used in the embeddable class To: dev@openjpa.apache.org In-Reply-To: <1257408405153-3950794.post@n2.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org In current openjpa implementation, version field in the embeddable is not s= upported. The rationale is embeddable is not an identifiable object, it can= not be modified independently of its owning entity, so there is no need fo= r the version field in the embeddable to keep track of its change. Also, un= like inheritance, the version field in the embeddable is not propogated to = its owning entity. Think of an example of an entity which has many embeddab= le fields or a collection of embeddables, if every embeddable has its own v= ersion field, and if they are all propagated to the owning entity, the owni= ng entity may end up with multiple version fields. which is not allowed. = =0A=0A=0A=0A=0A----- Original Message ----=0AFrom: "javadiahad@gmail.com" = =0ATo: dev@openjpa.apache.org=0ASent: Thu, November 5= , 2009 12:06:45 AM=0ASubject: version field dont work when used in the embe= ddable class=0A=0A=0AHi =0AIn my application I have an embeddable class tha= t contain some common fields=0Aincluding version field .when I put version = field in the main class=0Aeverything is good and OpenJPA increment the vers= ion field value and throw=0Aoptimistic exception when concurrent write occu= r .But when I put the version=0Afield on the embeddable class openJPA don= =E2=80=99t do anything. Is this is a bug=0Ain the OpenJPA ? or I am misusin= g the embeddable class?=0APlease help me=0AThanks=0AAhad Javadi=0A=0A-- =0A= View this message in context: http://n2.nabble.com/version-field-dont-work-= when-used-in-the-embeddable-class-tp3950794p3950794.html=0ASent from the Op= enJPA Developers mailing list archive at Nabble.com.=0A=0A=0A=0A