Return-Path: Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: (qmail 46493 invoked from network); 12 Mar 2009 18:13:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2009 18:13:30 -0000 Received: (qmail 69243 invoked by uid 500); 12 Mar 2009 18:13:29 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 69234 invoked by uid 500); 12 Mar 2009 18:13:29 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Received: (qmail 69223 invoked by uid 99); 12 Mar 2009 18:13:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 11:13:29 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@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; Thu, 12 Mar 2009 18:13:20 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LhpOt-0006Wn-AA for user@cayenne.apache.org; Thu, 12 Mar 2009 11:12:59 -0700 Message-ID: <22482429.post@talk.nabble.com> Date: Thu, 12 Mar 2009 11:12:59 -0700 (PDT) From: Francisco Peredo To: user@cayenne.apache.org Subject: Re: Object state after persist: consistent with JPA? In-Reply-To: <5adb61290903121100s2bfced46qa0c50b88b031e5fd@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: franciscoperedo@tabasco.gob.mx References: <22463349.post@talk.nabble.com> <5adb61290903111336t7ea4af67v9b931da9b206e307@mail.gmail.com> <5adb61290903111403u51c54caet60dc154446c192f7@mail.gmail.com> <22465074.post@talk.nabble.com> <205B0075-D46D-4319-8E9E-A7F8C039C166@puregumption.com> <22465578.post@talk.nabble.com> <109B261A-54A3-403B-83EC-FA193653C016@ish.com.au> <22477651.post@talk.nabble.com> <22481898.post@talk.nabble.com> <5adb61290903121100s2bfced46qa0c50b88b031e5fd@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Yes, but the thing is I already have some systems built with JPA/Hibernate, so I do need JPA compliace (maybe not full, but very close to full) Well, JPA has its own object context like feature, it is called "entityManager" the problem is that its API is poorer than Cayenne's API As I stated before, I really think someone should build a Cayenne like API that used any JPA compliant as its internal storage engine, JPA is just too low level Regards, Michael Gentry-2 wrote: > > Actually, Cayenne 3.0 final will probably *not* be JPA compliant. > Things change, of course, but that is my guess at this point. If > immediate JPA compliance is a requirement, Cayenne doesn't currently > meet that. The "Cayenne Classic" functionality, which is similar to > EOF, is in pretty good shape, though. > > Does JPA even offer the object context feature? To me, that is a huge > feature of Cayenne (and EOF). > > /dev/mrg > > > > -- View this message in context: http://www.nabble.com/Coming-from-EOF%3A-Cayenne-vs-Hibernate-tp22463349p22482429.html Sent from the Cayenne - User mailing list archive at Nabble.com.