cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JD Daniels" ...@datatrio.com>
Subject Re: Hibernate vs. OJB
Date Tue, 29 Jul 2003 16:47:46 GMT
The "persistence layer" was completely new to me as well. (It was Flow that
got me interested) Hibernate confuse dthe crap out of me. After Antonio's
wiki :http://wiki.cocoondev.org/Wiki.jsp?page=OJBWithJDO
well, JDO makes *sense* heh heh

What I mean is Antonios wiki I could get running and understand much quicker
than the Hugo burm's hibernate wiki.
(I think it is the difference betwen OJB and Hibernate, Not Antonio and hugo
;)

JD

----- Original Message -----
From: "Antonio Gallardo" <agallardo@agsoftware.dnsalias.com>
To: <dev@cocoon.apache.org>
Sent: Tuesday, July 29, 2003 12:26 AM
Subject: Re: Hibernate vs. OJB


> Leszek Gawron dijo:
> > Has anyone got any experiences? I am a complete "persistence layer
> > newbie", but I'd like to start a project using either Hibernate or OJB.
> > After 15 minutes of googling I got:
> >
> > http://www.freeroller.net/page/ceperez/20021213#why_i_don_t_like
> > http://www.porterhome.com/roller/page/matthew/20021212
> >
http://www.freeroller.net/page/ceperez/20021212#why_hibernate_is_better_than
>
> Hi:
>
> I did the same as you some days ago. I also check the dates of the links
> above. The docs are from the end of the last year. Since then, the OJB
> wake up and now is a very dynamic community. I invite you to join the
> community or check the mail archives.
>
> On the other way OJB can sports JDO, Hibernate not. What is all about this
> JDO?
>
> >From tutorial on developersworks of IBM:
> <snip>
> JDO is a Sun specification that aims to provide Java programmers with a
> much needed, lighweight view of OO persistent data. JDO frees developers
> to interact with objects in a natural way, providing an alternative to
> JDBC or Enterprise Java Beans with Bean Managed Persistence or Contained
> Managed Persistence.
>
> One of the biggest advantages is that JDO allow us to concentrate on
> developing a correct class model, rather than on developing a relational
> class model. Also JDO attempts to abstract the actual data source from the
> class model. This allow differents types of data sources to be "plugged
> in" to a deploy system.
> </snip>
>
> As I posted before the great advantage of OJB over Hibernate in our
> concrete case (Cocoon) is that OJB is another Apache Project. Hibernate is
> not an Apache project and his LGPL license is a problem for Cocoon. :(
>
> With OJB you can write the code using one of the 3 API avaliables:
>
> * PersistenceBroker
> * ODMG
> * JDO
>
> Best Regards,
>
> Antonio Gallardo
>
>
>


Mime
View raw message