rknr55 ;
I am not completely clear on what the read-write characteristics of other caching platforms are, but I assume it means that the cache writes through back to permanent storage on your behalf.
What I have observed with JBoss-Cache is that when you update an entity that is in cache, the cache, the cache is simply invalidated on write.
Here's an example of a remote call to a session bean, querying and persisting data.
Client:
Code:
client = clientService.getClient("886000003645");
JBoss Cache Shows:Code:
item: CacheEntry(com.foobar.Client)[NICK'S BIKE SHOP,886000003645]
Client:Code:
client = clientService.getClient("886000003645");
client.setClientName("BOB'S BIKE SHOP");
clientService.putObject(client);
JBoss Cache Shows:Code:
Nothing
Client:Code:
client = clientService.getClient("886000003645");
JBoss Cache Shows:Code:
item: CacheEntry(com.foobar.Client)[BOB'S BIKE SHOP,886000003645]
Hope that's helpful.
//Nicholas
Login
FAQ
Search