[
https://issues.jboss.org/browse/ISPN-7224?page=com.atlassian.jira.plugin....
]
Mike Noordermeer commented on ISPN-7224:
----------------------------------------
It's true that it sort-of adheres to the contract, but the whole sync flag becomes
fairly useless if it is not atomic. If the compute function was fast, I wouldn't need
caching, and if it isn't fast, I don't want to execute it multiple times.
The Spring contract also states 'If possible', and I do think it is possible to
lock the key (at least locally), so not 100% sure it fully matches the contract.
I'll see if I can work around it by overriding a couple of classes, thanks for your
reply.
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)