"[EMAIL PROTECTED]" wrote : | A cache is not a database. A database is, by definition, persistent storage so such behaviour is nonsensical for a db. And this is why caches delegate persistence to dbs - in JBC's case using a cache loader.
Umm, persistence is a relative term, valid within a certain scope. A local JB cache without cache loader indeed offers persistence within its operating environment, the JVM. The environment's execution entities, threads, can put objects into the cache, die, respawn and read them back from cache. Since the cache's storage environment, the heap, persists during the cache's life (even when the cache is stopped), there is no reason why the cache's own threads should be excluded from this mechanism and can't be restarted without losing data. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069082#4069082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069082 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
