[
https://issues.apache.org/jira/browse/IGNITE-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520800#comment-16520800
]
Valentin Kulichenko commented on IGNITE-8740:
---------------------------------------------
[~aakhmedov], can you please clarify how switching to {{ApplicationListener}}
fixes the issue? Is it guaranteed to be invoked later than
{{SmartInitializingSingleton#afterSingletonsInstantiated}}? I see the following
in the Javadoc which makes me doubt this:
{noformat}
* <p>This callback variant is somewhat similar to
* {@link org.springframework.context.event.ContextRefreshedEvent} but doesn't
* require an implementation of {@link
org.springframework.context.ApplicationListener},
* with no need to filter context references across a context hierarchy etc.
* It also implies a more minimal dependency on just the {@code beans} package
* and is being honored by standalone {@link ListableBeanFactory}
implementations,
* not just in an {@link org.springframework.context.ApplicationContext}
environment.
{noformat}
> 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)
