You say this data is "already in memory", how do you know?
Because I first put it myself in the cache. The data map already present in the cache node
(I checked with peek) has all the information I need, plus the
jboss:internal:uninitialized key which I don't need. When the cache finds that key, it
decides to load data from the cacheloader.
Also, the children are not loaded with their data until they are
accessed. This is a feature not a bug.
Well, I am calling getChildren() on a node, then getData() on the resulting map's
values. Again, I get the data I want with that extra key added. Am I doing it the wrong
way?
Some of the problems with JBCache 1.4 are caused by accessing data
via the Node object and not the Cache object.
Well, when I put data in the cache, I use the cache object. When I get data (in the first
case, without involving children), I use get(Fqn) on the cache object then getData() on
the node; I haven't found a better way to get all the node's data.
I found that if I manually remove the uninitialized key immediately after putting a node
in the cache, all the problems seem to disappear. However, this looks like an UGLY thing
to do.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057966#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...