[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: JDO

On Wed, 04 Apr 2001, Per Nyfelt wrote:
> We did discuss it a couple of weeks ago. The last version of the spec is not
> as strongly tied to a RDBMS as the previous drafts and there are some nice
> things such as an interesting java based query system and a relatively easy
> api from the client side. Implementing it does not seem to be done over
> night though. First of all the Connector architecture needs to be supported
> so if we want to support JDO we need to support the Connector api first.
> This would probably also lead to a possibility of integrating with EJB app
> servers since version 2 of the EJB spec has extended support for Connectors.
> For more info on the Connector architecture check out
> http://java.sun.com/j2ee/connector/.

The questions is: what is the goal of JDO. Will it become the Persistence
manager for EJB (I was told it will not but I'm still not sure) or will it be
an independent, more OO centric approach. If the later is true, then we
definitely should try to support it.


Falko

> 
> On another note, adding persistence to your normal Java objects is what you
> already have today with Ozone - no need to look at JDO for that.
> 
> Best regards,
> Per
> 
> 
> > -----Original Message-----
> > From: ozone-dev-owner@ozone-db.org
> > [mailto:ozone-dev-owner@ozone-db.org]On Behalf Of Joel Shellman
> > Sent: Sunday, April 01, 2001 6:40 AM
> > To: ozone-dev@ozone-db.org
> > Subject: JDO
> >
> >
> > I think I asked this before also, but can someone remind me why JDO is
> > not an interesting API for Ozone to support? I realize I haven't read
> > the spec yet, just a few overviews of it and such, but it sounds like
> > exactly the transparent persistence that I've wanted. You just create a
> > class and boom, it's basically automatically persistable--you don't have
> > to do anything to it. That's what I want. Just throw the object in the
> > db, and go on your merry way.
> >
> > Seems I remember someone mentioning that JDO is still tied to RDBMS
> > somehow. Is that so? If so, who can I send the really nasty email to
> > that obviously really deserves it for making a brand new "pure" (or so I
> > hoped) API tied to dead ugly legacy trash?
> >
> > :) No, I'm not usually this harsh--I'm just in a hurry, and I'm really
> > tired of trying to find the solutions I really need but no one else
> > seems to have implemented (at least, not in Free Software anyway).
> > --
> > Joel Shellman
> > KnOcean Interactive Corporation
> > http://www.knocean.com/
> >
> >
-- 
______________________________________________________________________
Falko Braeutigam                              mailto:falko@smb-tec.com
SMB GmbH                                        http://www.smb-tec.com