I had a look at CacheLoader's over the weekend, but not quite sure what I would 
actually need to implement. 

To 'build' the object that needs to be cached requires invoking a custom object 
which handles all the Data retrieval and building, and because of legacy code, 
there is _no_ concept of transactions or anything.

This object does not need to be persisted if changed (in fact this object 
should be immutable, but that's another story entirely), and only needs to be 
removed when other code deems that any cached value needs to be purged.

I just need to work out which method(s) in CacheLoader are responsible for the 
object retrieval when not in cache, and I assume the TreeCache can just handle 
the simple purge/remove situation.

>From  http://docs.jboss.org/jbcache/TreeCache.html#d0e354:

anonymous wrote : 
  | The CacheLoader interface has a set of methods that are called when no 
transactions are used: get(), put(), remove() and removeData(): they 
get/set/remove the value immediately. These methods are described as javadoc 
comments in the above interface.

I assume these are the methods I need to be concerned with?  The above URL 
mentions other methods which I believe I can basically ignore??? (no-op impl)



View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855126#3855126

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855126


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to