<?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 - Implementing Object Caching with AOP</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>Tue, 21 May 2013 11:27:34 -0400</pubDate>


    <item>

        <title>Implementing it differently</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[I think a better way of implementaiton would be<br><br>1. Let the original method getInterestRates(String prodGroup) always read from the cache.<br><br>2. Aspect will make sure that before the method getInterestRates(..)execution starts data is loaded to...]]></description>
        

        <pubDate>Thu, 12 May 2005 02:50:51 -0400</pubDate>

        

        <jf:creationDate>Thu, 12 May 2005 02:50:51 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 12 May 2005 02:50:51 -0400</jf:modificationDate>
        <jf:date>May 12, 2005</jf:date>
        <jf:author>MK P</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Implementing Object Caching with AOP</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[Ben, good point.<br><br>- Do not cache data what maybe already has been cached (hibernate, oracle.. others??...)<br><br>- Be carefull with storing data in mem (caching) vs. cloning/clustering applications.<br><br>- Be carefull with storing statefull data...]]></description>
        

        <pubDate>Thu, 21 Apr 2005 05:06:35 -0400</pubDate>

        

        <jf:creationDate>Thu, 21 Apr 2005 05:06:35 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 21 Apr 2005 05:06:35 -0400</jf:modificationDate>
        <jf:date>Apr 21, 2005</jf:date>
        <jf:author>Murat D??nmez</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Implementing Object Caching with AOP</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[Great article in general. ;-) <br><br>Just want to point out that for stateful data caching, cache aspect via AOP can be a great idea. But if we need caching mainly for entity data purpose, a good persistence layer (like Hibernate) also offers cache...]]></description>
        

        <pubDate>Wed, 20 Apr 2005 20:40:09 -0400</pubDate>

        

        <jf:creationDate>Wed, 20 Apr 2005 20:40:09 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 20 Apr 2005 20:40:09 -0400</jf:modificationDate>
        <jf:date>Apr 20, 2005</jf:date>
        <jf:author>Ben Wang</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Implementing Object Caching with AOP</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote><blockquote>My template for this is more along the lines of:value=cache.get(key);if (value==null){&amp;nbsp;&amp;nbsp;value=...&amp;nbsp;&amp;nbsp;cache.put(key,value)}return value;Not quite sure how your code template accomplishes what you...]]></description>
        

        <pubDate>Wed, 20 Apr 2005 07:02:46 -0400</pubDate>

        

        <jf:creationDate>Wed, 20 Apr 2005 07:02:46 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 20 Apr 2005 07:02:46 -0400</jf:modificationDate>
        <jf:date>Apr 20, 2005</jf:date>
        <jf:author>Juozas Baliuka</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>But in the real world...</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[I was just trying to emphasize the fact that you can use this kind of technology without using any AOP &quot;implementation product&quot; like AspectWerkz or AspectJ. It's possible to &quot;think AOP&quot; and apply it in pure Java, while waiting for the...]]></description>
        

        <pubDate>Wed, 20 Apr 2005 03:44:07 -0400</pubDate>

        

        <jf:creationDate>Wed, 20 Apr 2005 03:44:07 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 20 Apr 2005 03:44:07 -0400</jf:modificationDate>
        <jf:date>Apr 20, 2005</jf:date>
        <jf:author>Pierre Primot</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<div class="jive-quote">AOP let's you overcome the architect's dilemma. <br>&gt; You introduce new crosscutting concerns <br>&gt;(such as caching) when and if you need it. <br><br>What this ends up meaning still is that the application and the AOP have...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 20:27:53 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 20:27:53 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 20:27:53 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>valraven smith</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote>AOP let's you overcome the architect's dilemma. You introduce new crosscutting concerns (such as caching) when and if you need it. Using AOP, if at any point during evolution you realize the need for caching, you can introduce it without any...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 16:07:25 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 16:07:25 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 16:07:25 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>Cameron Purdy</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote><blockquote>One thing, I just realized that I'm talking about using Spring.</blockquote>Ah ok.  Then yes, you are correct, such a change would be completely at runtime.  AspectJ will require a recompilation of the aspect, though.--...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 15:15:12 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 15:15:12 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 15:15:12 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>David McCoy</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote>One thing, I just realized that I'm talking about using Spring.</blockquote>Ah ok.  Then yes, you are correct, such a change would be completely at runtime.  AspectJ will require a recompilation of the aspect, though.<br><br>-- <br>Cedric]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:58:40 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:58:40 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:58:40 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>Cedric Beust</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[A way to look at the cluttering issue is to realize that the sample application in the article is implementing at least two separate concerns: business logic and performance. Strictly from the business logic concern's point-of-view, the performance issue...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:52:57 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:52:57 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:52:57 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>Ramnivas Laddad</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote><blockquote><blockquote><blockquote>Interesting article, but I have a few issues with some of the AOP concepts discussed, which I summarized on my blog:<a href="http://beust.com/weblog/archives/000273.html"...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:48:24 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:48:24 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:48:24 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>David McCoy</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote><blockquote><blockquote>Interesting article, but I have a few issues with some of the AOP concepts discussed, which I summarized on my blog:<a href="http://beust.com/weblog/archives/000273.html"...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:47:00 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:47:00 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:47:00 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>David McCoy</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Implementing Object Caching with AOP</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote>My template for this is more along the lines of:<br>value=cache.get(key);<br>if (value==null)<br>{<br>&nbsp;&nbsp;value=...<br>&nbsp;&nbsp;cache.put(key,value)<br>}<br>return value;<br><br>Not quite sure how your code template accomplishes...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:46:43 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:46:43 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:46:43 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>Dmitriy Setrakyan</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>why not use a strategy object?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[<blockquote><blockquote>Interesting article, but I have a few issues with some of the AOP concepts discussed, which I summarized on my blog:<a href="http://beust.com/weblog/archives/000273.html"...]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:37:53 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:37:53 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:37:53 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>Cedric Beust</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>I agree</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=33382</link>

        

        
            <description><![CDATA[I have had this same thought since the first time I came across AOP. To me AOP is what J2EE designers (especially EJB designers) were trying to accomplish, but they ended up doing it in a clumsy way.]]></description>
        

        <pubDate>Tue, 19 Apr 2005 14:32:29 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Apr 2005 14:32:29 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Apr 2005 14:32:29 -0400</jf:modificationDate>
        <jf:date>Apr 19, 2005</jf:date>
        <jf:author>Sriram Gopalan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>



</channel>
</rss>

