> Incidentally EJB3 is going to be largely based on hibernate and sun
> have already signaled their intention that JDO and EJB are going to be
> dropped and a new standard created most likely playing catchup with
> Hibernate.

JDO and EJB are not going to be dropped: they're merged. The next
generation persistence API for J2SE/J2EE is being designed by people
from both JDO and EJB expert groups and also the lead developer of
Hibernate. And JDO is already competing well with Hibernate and JDO
2.0 is very powerful and flexible. It's no longer true to say that one
is better than another. From now on it's a matter of preference and
fanaticism. I, myself, prefer JDO because I think it's more
straightforward, easier to learn, and object oriented. Another person
may feel otherwise.

> Using JDO just because it is a "standard" is a bad idea, I've been
> there before and have difficulty trusting anything that gets designed
> by some self interested group of big companies, usually so they can
> make sure that your code only works with their libraries or IDE or app
> server because at the end of the day you usually have to do something
> that ties you to their implementation.

You're right that one should not use something only because it's a
standard, however JDO 2.0 is really powerful and flexible and has both
commercial and open-source implementations. It's not finalized yet but
most of the new features of this version are already integrated with
implementations like JPOX (open-source, in beta status) and Kodo JDO
(commercial).

> Runtime bytecode enhancement via cglib etc is the name of the game,
> having to add another pre-processing stage to your development cycle (
> as you must do with most implementations of jdo is soooo 2002 ).

Using XDoclet, at least with JPOX, this step can be continously
intergrated with your build process ;-)

I have not used Spring myself but I read somewhere that Spring
supports JDO (and Toplink and some other persistence frameworks) as
well.

For those of you who don't have a good feeling about JDO these two
articles from TheServerSide.com are very readable:

http://www.theserverside.com/articles/article.tss?l=JDOQueryPart1
http://www.theserverside.com/articles/article.tss?l=JDOQueryPart2

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to