[
https://issues.apache.org/jira/browse/IGNITE-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515023#comment-16515023
]
ASF GitHub Bot commented on IGNITE-8740:
----------------------------------------
GitHub user amirakhmedov opened a pull request:
https://github.com/apache/ignite/pull/4208
IGNITE-8740: Support reuse of already initialized Ignite in IgniteSpr…
…ingBean
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/amirakhmedov/ignite IGNITE-8740
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4208.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4208
----
commit f8cc9600a61e4f8398da422ebdabf13f4b85b197
Author: Amir Akhmedov <amir.akhmedov@...>
Date: 2018-06-17T08:18:11Z
IGNITE-8740: Support reuse of already initialized Ignite in IgniteSpringBean
----
> 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
> 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)
