If you plan to enable what Sanne is talking about, have a look at JPA 2 settings for cache
interaction. I think we have them nailed down properly with decent names and proper
separation between gets and puts.
On 6 août 2010, at 19:15, Sanne Grinovero <sanne.grinovero(a)gmail.com> wrote:
Hello,
I just noticed that the Flag.SKIP_CACHE_STORE will prevent my values
to be put in the store, but when using it with get() then the store is
still invoked; from the option name I was expecting it to skip lookup
too?
So I'm not sure how this was intended to work, should I clarify this
limitation in the javadocs or can I propose a fix to the
implementation, in case this wasn't intended?
I'd personally love to fix the implementation, as I've several use
cases in which this invocation is a useless yet expensive operation
for some types as the same flag is always used when putting in this
specific key types (and I can't use an additional differently
configured cache for it).
Cheers,
Sanne
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev