<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Sun renews its commitment to JDO with version 2.0</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Sat, 18 May 2013 19:26:01 -0400</pubDate>


    <item>

        <title>JDO != Lowest Common Denomenator</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[In an earlier posting to this thread, Christian commented:<blockquote>It is usually much (!) more important that the persistence tool makes all features and optimizations of the database accessible in an easy manner, instead of offering a least common...]]></description>
        

        <pubDate>Mon, 26 Apr 2004 12:20:29 -0400</pubDate>

        

        <jf:creationDate>Mon, 26 Apr 2004 12:20:29 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 26 Apr 2004 12:20:29 -0400</jf:modificationDate>
        <jf:date>Apr 26, 2004</jf:date>
        <jf:author>Robin Roos</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>jdo is great!</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[<blockquote>And if you want to take a look into it, you can read Robin Roos book for free as pdf.</blockquote>As Simon says, my book Java Data Objects is available in full as a downloadable PDF.  Of course I hope that some of you will choose to buy the...]]></description>
        

        <pubDate>Mon, 26 Apr 2004 11:44:37 -0400</pubDate>

        

        <jf:creationDate>Mon, 26 Apr 2004 11:44:37 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 26 Apr 2004 11:44:37 -0400</jf:modificationDate>
        <jf:date>Apr 26, 2004</jf:date>
        <jf:author>Robin Roos</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Diffrent API levels are intented to cooperate, not to fight</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[Saying that the JDO ability to manage various data storage is not an advantage - i.e. nobody changes its storage - is just the same as saying that JDBC ability to manage multiple RDBMS is not an advantage. Saying that JDBC drivers and SQL can handle...]]></description>
        

        <pubDate>Sun, 25 Apr 2004 13:54:15 -0400</pubDate>

        

        <jf:creationDate>Sun, 25 Apr 2004 13:54:15 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 25 Apr 2004 13:54:15 -0400</jf:modificationDate>
        <jf:date>Apr 25, 2004</jf:date>
        <jf:author>Jerome Beau</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Offline optimistic locking pattern</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[Ok, I will try to model it.<br>Let x is some data block and  asume read(x)/write(x) are atomic ( guaranteed by hardware). Sequences of primityve operations are atomic and isolated for concurent execution (guaranteed by DB...]]></description>
        

        <pubDate>Sat, 24 Apr 2004 06:17:55 -0400</pubDate>

        

        <jf:creationDate>Sat, 24 Apr 2004 06:17:55 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 24 Apr 2004 06:17:55 -0400</jf:modificationDate>
        <jf:date>Apr 24, 2004</jf:date>
        <jf:author>Juozas Baliuka</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Offline optimistic locking pattern</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[I barely know anything about JDO, but it sounds like what the parent post was referring to was the fact that these &quot;transactions&quot; will span multiple DB transactions, so even if the underlying connection has stronger guarantees than...]]></description>
        

        <pubDate>Sat, 24 Apr 2004 03:23:09 -0400</pubDate>

        

        <jf:creationDate>Sat, 24 Apr 2004 03:23:09 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 24 Apr 2004 03:23:09 -0400</jf:modificationDate>
        <jf:date>Apr 24, 2004</jf:date>
        <jf:author>Joe Cheng</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Offline optimistic locking pattern</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[<blockquote> This is not quite the same as a full-fledged optimistic transaction, since it does not necessarily share all the other characteristics of a transaction (in particular, since the offline optimistic lock spans multiple database connections,...]]></description>
        

        <pubDate>Sat, 24 Apr 2004 02:55:09 -0400</pubDate>

        

        <jf:creationDate>Sat, 24 Apr 2004 02:55:09 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 24 Apr 2004 02:55:09 -0400</jf:modificationDate>
        <jf:date>Apr 24, 2004</jf:date>
        <jf:author>Juozas Baliuka</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>flexibility vs. specialization</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[<blockquote><blockquote>It is usually much (!) more important that the persistence tool makes all features and optimizations of the database accessible in an easy manner, instead of offering a least common denimator API. </blockquote>Relational JDO...]]></description>
        

        <pubDate>Fri, 23 Apr 2004 23:40:30 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 23:40:30 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 23:40:30 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>Colin Sampaleanu</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>jdo is great!</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[I have been working with jdo for some months now and I can only say it's really nice.<br>I've tryed jdogenie(love the rmi support), kodo and lido so far and there is things I like about them all. And if you want to take a look into it, you can read Robin...]]></description>
        

        <pubDate>Fri, 23 Apr 2004 19:57:58 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 19:57:58 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 19:57:58 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>simon says</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>yikes</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[I guess I should not post when I just got off a plane and have jetlag. My bad, I was reacting to the quote and in my sleep deprived state I flamed you by mistake. Should have known better than to read TSS when I could barely keep my eyes open.]]></description>
        

        <pubDate>Fri, 23 Apr 2004 15:58:43 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 15:58:43 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 15:58:43 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>nextdb</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>flexibility vs. specialization</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[<blockquote>It is usually much (!) more important that the persistence tool makes all features and optimizations of the database accessible in an easy manner, instead of offering a least common denimator API. </blockquote>Relational JDO vendors all...]]></description>
        

        <pubDate>Fri, 23 Apr 2004 15:12:09 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 15:12:09 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 15:12:09 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>Abe White</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>JDO performance</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[How does JDO compare in production? Can anyone give examples of JDO performing better or worse at high volume? And have you measured why it&#x92;s better or worse?<br><br>Gary]]></description>
        

        <pubDate>Fri, 23 Apr 2004 13:18:44 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 13:18:44 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 13:18:44 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>Gary Struthers</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>flexibility vs. specialization</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[<blockquote>... for organizations which must have a get-out clause in case they find JDOQL can't actually do that one special query that the DBA has written, JDO 2.0 standardizes the way to access a SQL connection which is enlisted into the current...]]></description>
        

        <pubDate>Fri, 23 Apr 2004 09:57:39 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 09:57:39 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 09:57:39 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>rory Winston</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>flexibility vs. specialization</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[Interresting comments, Christian.<br><br>You claim that &quot;JDOQL is doomed until it supports all the capabilities of SQL&quot;.  Have you looked at any of the published material about JDOQL in JDO 2.0?  The query language has evolved significantly....]]></description>
        

        <pubDate>Fri, 23 Apr 2004 09:29:29 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 09:29:29 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 09:29:29 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>Robin Roos</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Sun renews its commitment to JDO with version 2.0</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[This is great news for the Java community. With JDO 2.0 we will have a mature standardized object-relational mapping solution for Java that doesn't suffer from some of the limitations of CMP EJB. JDO 1.0 does have some serious limitations but  it seems...]]></description>
        

        <pubDate>Fri, 23 Apr 2004 06:25:50 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 06:25:50 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 06:25:50 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>Andy Grove</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>flexibility vs. specialization</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=25460</link>

        

        
            <description><![CDATA[<blockquote>Second, because JDO is much more flexible than Hibernate.I'm not trying to degrade Hibernate in any way.  Hibernate is great for what it is: *relational* persistence for Java objects.  But JDO is much more; it can target any back end.  Kodo...]]></description>
        

        <pubDate>Fri, 23 Apr 2004 04:58:15 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Apr 2004 04:58:15 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Apr 2004 04:58:15 -0400</jf:modificationDate>
        <jf:date>Apr 23, 2004</jf:date>
        <jf:author>Christian Sell</jf:author>
        <jf:replyCount>6</jf:replyCount>
    </item>



</channel>
</rss>

