[
https://issues.jboss.org/browse/ISPN-7224?page=com.atlassian.jira.plugin....
]
Stéphane Nicoll commented on ISPN-7224:
---------------------------------------
What Mike said.
Sebastian, do you seriously expecting us to lock in a smart way in an abstraction while
stating at the same time you can't knowing what is actually happening behind the
scenes? I mean, the purpose of that separate method (and contract) is to give a chance for
cache implementations to do the right thing. I think that's pretty obvious we
can't do that with our abstraction.
That extra method is also only called when the sync flag is true and we ask [users to
refer to the doc of the cache provider for more
details|http://docs.spring.io/spring-framework/docs/current/spring-framework-reference/htmlsingle/#cache-annotations-cacheable-synchronized].
Whatever you decide to do should probably be explicitly documented.
Thanks!
Support synchronous get in Spring's cache abstraction
-----------------------------------------------------
Key: ISPN-7224
URL:
https://issues.jboss.org/browse/ISPN-7224
Project: Infinispan
Issue Type: Feature Request
Components: Spring Integration
Reporter: Stéphane Nicoll
Assignee: Sebastian Łaskawiec
Priority: Critical
Fix For: 9.0.0.Beta1, 9.0.0.Final
Spring Framework 4.3 has introduced a read-through option See
https://jira.spring.io/browse/SPR-9254 for more details. In practice this would require
you to compile against 4.3 and implement the additional method.
The code is meant to be backward compatible with previous version, as long as you're
guarding the new exception in an inner class, see [this implementation for an
example|https://github.com/hazelcast/hazelcast/blob/37ba79c4a8d35617c5f6a...]
Let me know if I can help.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)