Re: [jbosscache-issues] JBoss cache architecture question
So given the TreeCache's architecture, there doesn't seem to be any
way to use the existing CacheLoaders to easily do what I want.
If you absolutely
wanted to use an existing implementation, your second
approach looks viable to me. But then again, and as you pointed out,
you'd be returning an entire map for every single piece of data.
And, most importantly, is there any non-complex way for me to use
JBoss Cache to serve as record-level front-end cache to a database
like I'm trying to do?
You're free to write your own cache loader from
scratch, or even extend
one of the existing ones. One solution might be to try and implement
your second suggestion as the underlying details to your custom loader
solution. In this manner, you might be able to hide the complexity
behind the CacheLoader API but still achieve what you're looking to do
via some under-the-cover fqn munging.
-joseph