Yes, you can suppress the cache loader from writing by setting ignoreModifications to true in your cache loader cfg.
And yes, in this case wasRemovedInTx() will prevent the value from being loaded from the cache loader - this is an optimisation since in MOST cache loaders this would result in a null coming back anyway, after hitting the disk. But I see what you mean in that this does impair on the *correctness* of behaviour when ignoreModifications is true. Feel free to create a JIRA for this and vote for it. And regarding loading externally, you could use Cache.putForExternalRead() which is built for the purpose of doing a put which is a result of a read from an external data source (as opposed to a put() which is a write to the external data source as well, such as a new item in the cache and data source). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157592#4157592 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157592 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
