<?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 - Feasibility of using Optimistic Locking managing</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 03:18:07 -0400</pubDate>


    <item>

        <title>Feasibility of using Optimistic Locking managing</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=40089</link>

        

        
            <description><![CDATA[This case is definatley a caveat . A possible solution could be putting the call to updateVersion() in synchronized block . But it is highly discouraged in EJB environment as u never know the behaviour of the container .It could be multiple instances for...]]></description>
        

        <pubDate>Thu, 27 Apr 2006 09:40:01 -0400</pubDate>

        

        <jf:creationDate>Thu, 27 Apr 2006 09:40:01 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 27 Apr 2006 09:40:01 -0400</jf:modificationDate>
        <jf:date>Apr 27, 2006</jf:date>
        <jf:author>Debashish Ghosh</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Feasibility of using Optimistic Locking managing</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=40089</link>

        

        
            <description><![CDATA[Thnx Debashish.<br>&nbsp;&nbsp;&nbsp;Suppose I use Read_Commited. Than, what happens when say at a rare instance, Two clients read the exact same data at the exact same time &amp; passed checkAndUpdateVersion(). say the version was 10 before and they...]]></description>
        

        <pubDate>Wed, 26 Apr 2006 23:52:13 -0400</pubDate>

        

        <jf:creationDate>Wed, 26 Apr 2006 23:52:13 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 26 Apr 2006 23:52:13 -0400</jf:modificationDate>
        <jf:date>Apr 26, 2006</jf:date>
        <jf:author>Sajid Moinuddin</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Feasibility of using Optimistic Locking managing</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=40089</link>

        

        
            <description><![CDATA[Sajid,<br>&nbsp;&nbsp;&nbsp;I would assume that before update u extract the actual version value from db and compare it with that of DTO . U can safely use the isolation level READ_UNCOMMITTED which is the most efficient but allow all dirty,repeatable...]]></description>
        

        <pubDate>Wed, 26 Apr 2006 11:09:13 -0400</pubDate>

        

        <jf:creationDate>Wed, 26 Apr 2006 11:09:13 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 26 Apr 2006 11:09:13 -0400</jf:modificationDate>
        <jf:date>Apr 26, 2006</jf:date>
        <jf:author>Debashish Ghosh</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Feasibility of using Optimistic Locking managing</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=40089</link>

        

        
            <description><![CDATA[Hi all,<br>I am using versioning for optimistic locking pattern as described in ejb design pattern. all by business operations takes DTOs and does bulk operation. Now, I am keeping a version cmp field in my dtos and programatically increasing it for each...]]></description>
        

        <pubDate>Tue, 25 Apr 2006 06:34:05 -0400</pubDate>

        

        <jf:creationDate>Tue, 25 Apr 2006 06:34:05 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 25 Apr 2006 06:34:05 -0400</jf:modificationDate>
        <jf:date>Apr 25, 2006</jf:date>
        <jf:author>Sajid Moinuddin</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>



</channel>
</rss>

