cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luca Garulli <l.garu...@gmail.com>
Subject Re: Daisy as CMS: why don't use JDO?
Date Thu, 14 Oct 2004 09:08:33 GMT
On Wed, 13 Oct 2004 21:29:49 +0200, Ugo Cei <ugo@apache.org> wrote:
> Il giorno 13/ott/04, alle 19:22, Luca Garulli ha scritto:
> 
> > This is the point. Using JDO allow you to switch the JDO
> > implementation and obviously repository without lock to a product!!!
> > Isn't enought?
> > I don't speak about product preference. I'm talking of STANDARD. JDO
> > is a STANDARD.
> 
> If this were true, everyone would be using JDO exclusively by now. JDBC
> is as much a standard as JDO and SQL even more so.
> 

Sorry but I didn't want to start a flame..

If you use JDBC you had to develop the Object/Relational mapping for
your "persistent classes" !!! Let's use JDO and you don't worry about
OR mapping. Dot.

Everyone has own preferences about OR mapping. Surely it was better to
use OJB (or any others) rather than writing this task by hand.

I don't want to teach to anyone why it's better to not reinvent the wheel.

Using a (good) standard such as JDO allows much more portability and
performance.

That's all folks.

bye,
Luca Garulli
OrienTechnologies.com
(the light ODBMS, all in one JDO solution)

Mime
View raw message