[ https://issues.apache.org/jira/browse/IGNITE-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Semyon Danilov updated IGNITE-13169: ------------------------------------ Description: At the moment IgniteRepositoryFactoryBean requires Ignite instance bean (or IgniteConfiguration instance bean) with specific name. There are couple of problems with that behavior: 1) We have a SpringBoot autoconfiguration module which creates bean with different name, so Ignite Spring Data won't work out of the box 2) That is, actually, not a Spring-way to do things: Spring prefers injecting by class, qualifiers like name and order should be used only when necessay I propose changing behavior to "getting bean by class and not by name" was:At the moment Repository Factory Bean > Remove Ignite bean name requirement for Spring Data Repository > -------------------------------------------------------------- > > Key: IGNITE-13169 > URL: https://issues.apache.org/jira/browse/IGNITE-13169 > Project: Ignite > Issue Type: Improvement > Components: springdata > Affects Versions: 2.8.1 > Reporter: Semyon Danilov > Assignee: Semyon Danilov > Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > At the moment IgniteRepositoryFactoryBean requires Ignite instance bean (or > IgniteConfiguration instance bean) with specific name. > There are couple of problems with that behavior: > 1) We have a SpringBoot autoconfiguration module which creates bean with > different name, so Ignite Spring Data won't work out of the box > 2) That is, actually, not a Spring-way to do things: Spring prefers injecting > by class, qualifiers like name and order should be used only when necessay > I propose changing behavior to "getting bean by class and not by name" -- This message was sent by Atlassian Jira (v8.3.4#803005)