[
https://issues.apache.org/jira/browse/IGNITE-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678129#comment-16678129
]
Luís Alves commented on IGNITE-8740:
------------------------------------
Hi,
I think SmartInitializingSingleton#afterSingletonsInstantiated is too late.
Did you try with IgniteRepository?
It's a Singleton that require Ignite to be started and Ignite only starts after
all Singletons are instantiated.
My current setup complains that:
@RepositoryConfig(cacheName = IgniteConfig.SERVER_KEY_CACHE)
public interface ServerKeyRepository extends IgniteRepository<ServerKey,
String>
cannot be created because ignite is not running.
> Support reuse of already initialized Ignite in IgniteSpringBean
> ---------------------------------------------------------------
>
> Key: IGNITE-8740
> URL: https://issues.apache.org/jira/browse/IGNITE-8740
> Project: Ignite
> Issue Type: Improvement
> Components: spring
> Affects Versions: 2.4
> Reporter: Ilya Kasnacheev
> Assignee: Amir Akhmedov
> Priority: Blocker
> Fix For: 2.6
>
>
> See
> http://apache-ignite-users.70518.x6.nabble.com/IgniteSpringBean-amp-Ignite-SpringTransactionManager-broken-with-2-4-td21667.html#a21724
> (there's patch available)
> The idea is to introduce a workaround for users hit by IGNITE-6555, which
> unfortunately broke some scenarios.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
