Typo. The code example should have been:
public final void cache(Object somethingToCache, ReplicationMode
replicationMode) throws ServiceException
{
TreeCache treeCache = mTreeCache;
Fqn typePath = MetadataCachePaths.typePathFor(somethingToCache);
if ((replicationMode == ReplicationMode.Repl
We have some followup questions. We are writing unit tests that operate out of
container and with the TreeCache not clustered.
When we create the TreeCache locally for out-of-container testing, we call
setCacheMode(TreeCache.LOCAL):
TreeCache theTreeCache = new TreeCache();
theTreeCache.setCach
However, we also do puts to the cache that we want to replication. What we
really want is:
if put due to read from database
setCacheLModeLocal(true)
else
setCacheModeLocal(false)
end if
But with puts to the cache happening in multiple nodes, and puts due to reads
happening in other nodes, won't
Very cool--thanks!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174368#4174368
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174368
___
jboss-user mailing list
jboss-user@l
Is there a put method we can call that doesn't cause replication? If so, we
would not have to implement a CacheLoader, which would save a fair amount of
time.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174362#4174362
Reply to the post :
http://www.jboss
Thank you for the clarification. We will implement a CacheLoader now that we
understand the distinction.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174361#4174361
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41743
We are very happy with TreeCache and CacheLoader--the documentation for both is
first-rate, and the code works perfectly in our application.
However, there is one thing about the design that puzzles us, and we're hoping
you can explain it.
In our implementation, we currently don't use a CacheLo
