[
https://issues.apache.org/jira/browse/IGNITE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170575#comment-16170575
]
Valentin Kulichenko commented on IGNITE-2786:
---------------------------------------------
[~bbarin] Are you saying that Spring does it's own caching anyway? If so, then
I believe {{caches}} map can be removed altogether.
As for you solution: do I understand correctly that {{CacheErrorHandler}} has
to be configured as a separate bean? If that's the case, I don't like it, as
the discussed case has to be handled by {{SpringCacheManager}} automatically. I
think it can be easily done in {{SpringCache}} class.
> SpringCache doesn't survive client reconnect
> --------------------------------------------
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't
> be used, because existing cache instance are closed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
