[
https://issues.apache.org/jira/browse/IGNITE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938258#comment-15938258
]
Vyacheslav Daradur commented on IGNITE-4211:
--------------------------------------------
[~avinogradov]
{quote}
> it is very strange test
Next rule is: each contributor should figure it out how current solution work
before proposing replacement.
{quote}
The test class is strange for me, not because I didn't figure it out, but
because it had strange behavior.
Following examples confirm this:
bq. Please write an example showing this.
{code}
/** {@inheritDoc} */
@SuppressWarnings("unchecked")
@Override public <T> T get(Object key, Class<T> type) {
return null;
}
{code}
And run all tests in the GridSpringCacheManagerSelfTest. Result = green light.
Same behaviour with new-get-method.
@Cachable calls only simple get-method "public ValueWrapper get(Object key)"
bq. BTW, any ideas why it's not covered by @CachePut?
I think @CachePut calls only "public void put(Object key, Object val)".
But I don't want to discuss about it, it's not relate to this issue.
I'll remake test according to your recomendations, soon.
> Update Spring dependency to latest stable version
> -------------------------------------------------
>
> Key: IGNITE-4211
> URL: https://issues.apache.org/jira/browse/IGNITE-4211
> Project: Ignite
> Issue Type: Improvement
> Components: build
> Affects Versions: 1.7
> Reporter: Sergey Kozlov
> Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still
> uses 4.1.0 released two years ago. Could we to update to latest stable
> version (4.3.4 at the moment)?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
