Hey Andy, Thanks a lot for the info. I agree with you that JPA is driven by large corporations and all they want is to become standardized in some way. That's why I want to get a feeling from people working with JDO as I find it more complete and robust. I've been thru JPA specification and found it very tightly coupled with relational database, not to mention the use of annotations kind of polutes the code. Regarding your question about JDOQL, I was told that JDOQL would not support things like BETWEEN. I don't have much more info about particular features, but I will try to find them out and let you know.
BTW, I've been trying to get Teneo EMF and JPOX plugin working, but had not luck so far. Has anybody got it working ? I am getting an ArrayIndexOutOfBoundsException at org.eclipse.emf.teneo.jpox.mapper.GenerateJDO.main(GenerateJDO.java:74) when generating the EMF - JDO/JPOX OR mapping. I couldn't find any solution on internet. FYI, I think a must would be having more available tools, such as eclipse plugins, in order to get more people using JDO. Thanks, Dário -----Original Message----- From: Andy Jefferson [mailto:[EMAIL PROTECTED] Sent: sexta-feira, 20 de outubro de 2006 05:26 To: jdo-dev@db.apache.org; Dário Luís Coneglian Oliveros Subject: Re: The Future of JDO > By reading this thread and an article posted by Linda DeMichiel and Craig > Russell (http://java.sun.com/j2ee/letter/persistence.html), I was quite > confused about which one (JDO or JPA) to choose as many efforts have been > pushed towards JSR-220 so far. I know JPA is mainly driven by vendors, > however I've heard its query language is quite powerful when compared to > JDOQL. Any comments would be appreciated. Hi Dario, A correction. JPA is driven by large corporations and politics. There are actually many vendors of JDO (the majority with JDO1 solutions, but some with JDO2 solutions). I personally would not base any decision on what you hear. Large corporations say many things and put forward many statements about their preferred technology based on their own balance sheet and not on capability of the technology. You should base your decisions on what the specifications actually say and what implementations do and what you require. On JPOX we put together a brief comparison of JDO2 and JPA1 http://www.jpox.org/docs/persistence_technology.html This has been on our site for people to comment/disagree with. There are other such comparisons around, all coming up with the same basic opinion. Here are a couple http://www.jroller.com/page/matthewadams?entry=quick_comparison_of_ejb_3 http://jroller.com/page/ThoughtPark?entry=ejb3_persistence_an_inferior_standard Any particular feature of JPQL/JDOQL you are referring to ? -- Andy
