hopefully the new specification will be backward compatible with JDO 1.0.1, so that those of us with JDO-based applications today (and those building apps with persistence requirements between now and 2006) will have a...]]> Sat, 26 Feb 2005 19:51:37 -0500 Sat, 26 Feb 2005 19:51:37 -0500 Sat, 26 Feb 2005 19:51:37 -0500 Feb 26, 2005 Tony Vai 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995

JDBC is fine for small applications. For a large scale application with 50 tables you're looking at 4+ CRUD operations per table. That's 50 * 4 = 200 flippin' JDBC calls! Now, let's PRAY that you didn't hard code those into the...]]> Wed, 19 Jan 2005 16:12:59 -0500 Wed, 19 Jan 2005 16:12:59 -0500 Wed, 19 Jan 2005 16:12:59 -0500 Jan 19, 2005 vik sheth 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995
I'm not an expert on persistence APIs, but there does seem to be a common theme here with regards to the JCP process. What I see is a lot of standardisation too early. Why not let a number of solutions compete for mind share, and then after...]]> Tue, 04 Jan 2005 07:08:14 -0500 Tue, 04 Jan 2005 07:08:14 -0500 Tue, 04 Jan 2005 07:08:14 -0500 Jan 4, 2005 Paul Beckford 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 The information about the new common persistence API in EJB3.0 worried me: The API is is the old EJB entity API (but now...]]> Sat, 18 Dec 2004 09:34:32 -0500 Sat, 18 Dec 2004 09:34:32 -0500 Sat, 18 Dec 2004 09:34:32 -0500 Dec 18, 2004 Steven Sagaert 2 http://www.theserverside.com/discussions/thread.tss?thread_id=28995

JDBC is fine for small applications. For a large scale application with 50 tables you're looking at 4+ CRUD operations per table. That's 50 * 4 = 200 flippin' JDBC calls! Now, let's PRAY that you didn't hard code those into the...]]> Fri, 12 Nov 2004 19:52:37 -0500 Fri, 12 Nov 2004 19:52:37 -0500 Fri, 12 Nov 2004 19:52:37 -0500 Nov 12, 2004 Martin N. 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 Thu, 28 Oct 2004 22:35:40 -0400 Thu, 28 Oct 2004 22:35:40 -0400 Thu, 28 Oct 2004 22:35:40 -0400 Oct 28, 2004 Jim Huang 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 Thu, 28 Oct 2004 17:30:36 -0400 Thu, 28 Oct 2004 17:30:36 -0400 Thu, 28 Oct 2004 17:30:36 -0400 Oct 28, 2004 Frank LaRosa 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 I know...I worked with it

Thats not what I remember... you have worked with very little of it. Plent of talk about it though... :-)]]> Thu, 30 Sep 2004 23:00:49 -0400 Thu, 30 Sep 2004 23:00:49 -0400 Thu, 30 Sep 2004 23:00:49 -0400 Sep 30, 2004 Nick Minutello 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 So why should I bother Hibernate?

Probably because Hibernate has more users than all the JDO vendors put together?
Being on a small-userbase product puts you firmly on the bug-finding path...

Large-scale vendor adoption...]]> Thu, 30 Sep 2004 22:56:38 -0400 Thu, 30 Sep 2004 22:56:38 -0400 Thu, 30 Sep 2004 22:56:38 -0400 Sep 30, 2004 Nick Minutello 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 However, we specifically will not require that a relational backing store be used with the persistence API. This allows vendors to supply implementations of the standard that support non-relational data stores. For example, the TCK for the...]]> Thu, 30 Sep 2004 13:23:10 -0400 Thu, 30 Sep 2004 13:23:10 -0400 Thu, 30 Sep 2004 13:23:10 -0400 Sep 30, 2004 Juozas Baliuka 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995

what you are describing already exists and is called JDO. What's the reason to drop the JDO EG work and use the EJB 3.0 draft developed by a team with O/R mapping background?

The JDO 2.0 work is not being dropped. It...]]> Thu, 30 Sep 2004 06:28:35 -0400 Thu, 30 Sep 2004 06:28:35 -0400 Thu, 30 Sep 2004 06:28:35 -0400 Sep 30, 2004 Erik Bengtson 0 http://www.theserverside.com/discussions/thread.tss?thread_id=28995 what you are describing already exists and is called JDO. What's the reason to drop the JDO EG work and use the EJB 3.0 draft developed by a team with O/R mapping background?