Why spring boot does not load beans configuration in order?
When i try to run a spring boot project, it tolde me that it can not autowire some beans whitch are instanciated in a configuration classes.
I think that spring can not load those configuration classes in order.
The stack trace : no bean found the be autowired Ignite<Long,MyEntity> myEntityCache in MyDao
Here is the source :
The main class
@SpringBootApplication
// The beans in the IgniteConfig have to be loaded before dao, service, and Controller
@ComponentScan(basePackageClasses={IgniteConfig.class,AppConfig.class})
public class DemoIgnite {
public static void main(String args) {
SpringApplication.run(DemoIgnite .class, args);
}
}
Config Class 1
@Configuration
public class IgniteConfig {
@Bean
public SpringContext springContext() {
return new SpringContext();
}
@Bean
public Ignite igniteInstance(@Autowired SpringContext springContext) {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName("instance");
List<CacheConfiguration> ccDas = new ArrayList<>();
CacheConfiguration cch = new CacheConfiguration<>("myEntitycache");
cch.setCacheMode(CacheMode.REPLICATED);
cch.setIndexedTypes(Long.class, myEntity.class);
ccDas.add(cch);
cfg.setCacheConfiguration( ccDas.toArray(new CacheConfiguration[0]));
SpringCacheManager springCacheManager = new SpringCacheManager();
springCacheManager.setConfiguration(cfg);
return Ignition.start(cfg);
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache(@Autowired Ignite igniteInstance) {
return igniteInstance.cache("myEntitycache");
}
Config class 2
@Configuration
@ComponentScan({
"com.demo.repository",
"com.demo.service",
"com.demo.controller"
})
public class AppConfig {
}
Dao class
@Repository
public class MyDao{
@Autowired
private Ignite<Long,MyEntity> myEntityCache;
...
Service class:
@Service
public class MyService{
@Autowird
private MyDao dao;
...
Controller class:
@RestController
@RequestMapping
public class MyController{
@Autowired
private MyService service;
....
spring spring-boot
add a comment |
When i try to run a spring boot project, it tolde me that it can not autowire some beans whitch are instanciated in a configuration classes.
I think that spring can not load those configuration classes in order.
The stack trace : no bean found the be autowired Ignite<Long,MyEntity> myEntityCache in MyDao
Here is the source :
The main class
@SpringBootApplication
// The beans in the IgniteConfig have to be loaded before dao, service, and Controller
@ComponentScan(basePackageClasses={IgniteConfig.class,AppConfig.class})
public class DemoIgnite {
public static void main(String args) {
SpringApplication.run(DemoIgnite .class, args);
}
}
Config Class 1
@Configuration
public class IgniteConfig {
@Bean
public SpringContext springContext() {
return new SpringContext();
}
@Bean
public Ignite igniteInstance(@Autowired SpringContext springContext) {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName("instance");
List<CacheConfiguration> ccDas = new ArrayList<>();
CacheConfiguration cch = new CacheConfiguration<>("myEntitycache");
cch.setCacheMode(CacheMode.REPLICATED);
cch.setIndexedTypes(Long.class, myEntity.class);
ccDas.add(cch);
cfg.setCacheConfiguration( ccDas.toArray(new CacheConfiguration[0]));
SpringCacheManager springCacheManager = new SpringCacheManager();
springCacheManager.setConfiguration(cfg);
return Ignition.start(cfg);
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache(@Autowired Ignite igniteInstance) {
return igniteInstance.cache("myEntitycache");
}
Config class 2
@Configuration
@ComponentScan({
"com.demo.repository",
"com.demo.service",
"com.demo.controller"
})
public class AppConfig {
}
Dao class
@Repository
public class MyDao{
@Autowired
private Ignite<Long,MyEntity> myEntityCache;
...
Service class:
@Service
public class MyService{
@Autowird
private MyDao dao;
...
Controller class:
@RestController
@RequestMapping
public class MyController{
@Autowired
private MyService service;
....
spring spring-boot
Instead of taking them as a parameter, try callling igniteInstance() in myEntityCache(), and remove the parameter from igniteInstance() (as it doesn't seem to need the SpringContext for anything.. Spring usually finds all possible beans first, before creating any - so order of declaration should not matter... (I think that, as long as you have no cycles, it will order them as needed...).
– moilejter
Nov 11 at 23:24
add a comment |
When i try to run a spring boot project, it tolde me that it can not autowire some beans whitch are instanciated in a configuration classes.
I think that spring can not load those configuration classes in order.
The stack trace : no bean found the be autowired Ignite<Long,MyEntity> myEntityCache in MyDao
Here is the source :
The main class
@SpringBootApplication
// The beans in the IgniteConfig have to be loaded before dao, service, and Controller
@ComponentScan(basePackageClasses={IgniteConfig.class,AppConfig.class})
public class DemoIgnite {
public static void main(String args) {
SpringApplication.run(DemoIgnite .class, args);
}
}
Config Class 1
@Configuration
public class IgniteConfig {
@Bean
public SpringContext springContext() {
return new SpringContext();
}
@Bean
public Ignite igniteInstance(@Autowired SpringContext springContext) {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName("instance");
List<CacheConfiguration> ccDas = new ArrayList<>();
CacheConfiguration cch = new CacheConfiguration<>("myEntitycache");
cch.setCacheMode(CacheMode.REPLICATED);
cch.setIndexedTypes(Long.class, myEntity.class);
ccDas.add(cch);
cfg.setCacheConfiguration( ccDas.toArray(new CacheConfiguration[0]));
SpringCacheManager springCacheManager = new SpringCacheManager();
springCacheManager.setConfiguration(cfg);
return Ignition.start(cfg);
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache(@Autowired Ignite igniteInstance) {
return igniteInstance.cache("myEntitycache");
}
Config class 2
@Configuration
@ComponentScan({
"com.demo.repository",
"com.demo.service",
"com.demo.controller"
})
public class AppConfig {
}
Dao class
@Repository
public class MyDao{
@Autowired
private Ignite<Long,MyEntity> myEntityCache;
...
Service class:
@Service
public class MyService{
@Autowird
private MyDao dao;
...
Controller class:
@RestController
@RequestMapping
public class MyController{
@Autowired
private MyService service;
....
spring spring-boot
When i try to run a spring boot project, it tolde me that it can not autowire some beans whitch are instanciated in a configuration classes.
I think that spring can not load those configuration classes in order.
The stack trace : no bean found the be autowired Ignite<Long,MyEntity> myEntityCache in MyDao
Here is the source :
The main class
@SpringBootApplication
// The beans in the IgniteConfig have to be loaded before dao, service, and Controller
@ComponentScan(basePackageClasses={IgniteConfig.class,AppConfig.class})
public class DemoIgnite {
public static void main(String args) {
SpringApplication.run(DemoIgnite .class, args);
}
}
Config Class 1
@Configuration
public class IgniteConfig {
@Bean
public SpringContext springContext() {
return new SpringContext();
}
@Bean
public Ignite igniteInstance(@Autowired SpringContext springContext) {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName("instance");
List<CacheConfiguration> ccDas = new ArrayList<>();
CacheConfiguration cch = new CacheConfiguration<>("myEntitycache");
cch.setCacheMode(CacheMode.REPLICATED);
cch.setIndexedTypes(Long.class, myEntity.class);
ccDas.add(cch);
cfg.setCacheConfiguration( ccDas.toArray(new CacheConfiguration[0]));
SpringCacheManager springCacheManager = new SpringCacheManager();
springCacheManager.setConfiguration(cfg);
return Ignition.start(cfg);
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache(@Autowired Ignite igniteInstance) {
return igniteInstance.cache("myEntitycache");
}
Config class 2
@Configuration
@ComponentScan({
"com.demo.repository",
"com.demo.service",
"com.demo.controller"
})
public class AppConfig {
}
Dao class
@Repository
public class MyDao{
@Autowired
private Ignite<Long,MyEntity> myEntityCache;
...
Service class:
@Service
public class MyService{
@Autowird
private MyDao dao;
...
Controller class:
@RestController
@RequestMapping
public class MyController{
@Autowired
private MyService service;
....
spring spring-boot
spring spring-boot
asked Nov 11 at 23:13
TinyOS
7691828
7691828
Instead of taking them as a parameter, try callling igniteInstance() in myEntityCache(), and remove the parameter from igniteInstance() (as it doesn't seem to need the SpringContext for anything.. Spring usually finds all possible beans first, before creating any - so order of declaration should not matter... (I think that, as long as you have no cycles, it will order them as needed...).
– moilejter
Nov 11 at 23:24
add a comment |
Instead of taking them as a parameter, try callling igniteInstance() in myEntityCache(), and remove the parameter from igniteInstance() (as it doesn't seem to need the SpringContext for anything.. Spring usually finds all possible beans first, before creating any - so order of declaration should not matter... (I think that, as long as you have no cycles, it will order them as needed...).
– moilejter
Nov 11 at 23:24
Instead of taking them as a parameter, try callling igniteInstance() in myEntityCache(), and remove the parameter from igniteInstance() (as it doesn't seem to need the SpringContext for anything.. Spring usually finds all possible beans first, before creating any - so order of declaration should not matter... (I think that, as long as you have no cycles, it will order them as needed...).
– moilejter
Nov 11 at 23:24
Instead of taking them as a parameter, try callling igniteInstance() in myEntityCache(), and remove the parameter from igniteInstance() (as it doesn't seem to need the SpringContext for anything.. Spring usually finds all possible beans first, before creating any - so order of declaration should not matter... (I think that, as long as you have no cycles, it will order them as needed...).
– moilejter
Nov 11 at 23:24
add a comment |
1 Answer
1
active
oldest
votes
This means that you don't have a bean of Ignite<Long,MyEntity>
type in your context. Moreover springContext
bean seems redundant, it's not used by igniteInstance
bean. As pointed out by moilejter it probably should be:
IgniteConfig
@Bean
public Ignite ignite() {
...
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache() {
return ignite().cache("myEntitycache");
}
MyDao
@Repository
public class MyDao {
@Autowired
private IgniteCache<Long, MyEntity> myEntityCache;
...
}
In principle Spring performs the bean setup in few phases as explained in chapter 1.3.2. Instantiating Beans docs:
Bean definition discovery - resources like
@Configuration
classes orXML
files are scanned and bean signatures are collected.Eager beans instantiation e.g. singletons - from the definitions collected in point 1 while resolving dependencies between definitions. That's why there is no explicit bean instantiation order as the process is driven from dependencies.
Lazy beans instantiation e.g.
@Lazy
annotated - when the context is already up, this beans will be constructed only when accessed from code.
1
I think this is right - the client is asking for aIgnite<Long,MyEntity>
but the configuration defines aIgniteCache<Long, MyEntity>
- which seems like a different type ...
– moilejter
Nov 11 at 23:41
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254191%2fwhy-spring-boot-does-not-load-beans-configuration-in-order%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This means that you don't have a bean of Ignite<Long,MyEntity>
type in your context. Moreover springContext
bean seems redundant, it's not used by igniteInstance
bean. As pointed out by moilejter it probably should be:
IgniteConfig
@Bean
public Ignite ignite() {
...
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache() {
return ignite().cache("myEntitycache");
}
MyDao
@Repository
public class MyDao {
@Autowired
private IgniteCache<Long, MyEntity> myEntityCache;
...
}
In principle Spring performs the bean setup in few phases as explained in chapter 1.3.2. Instantiating Beans docs:
Bean definition discovery - resources like
@Configuration
classes orXML
files are scanned and bean signatures are collected.Eager beans instantiation e.g. singletons - from the definitions collected in point 1 while resolving dependencies between definitions. That's why there is no explicit bean instantiation order as the process is driven from dependencies.
Lazy beans instantiation e.g.
@Lazy
annotated - when the context is already up, this beans will be constructed only when accessed from code.
1
I think this is right - the client is asking for aIgnite<Long,MyEntity>
but the configuration defines aIgniteCache<Long, MyEntity>
- which seems like a different type ...
– moilejter
Nov 11 at 23:41
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
add a comment |
This means that you don't have a bean of Ignite<Long,MyEntity>
type in your context. Moreover springContext
bean seems redundant, it's not used by igniteInstance
bean. As pointed out by moilejter it probably should be:
IgniteConfig
@Bean
public Ignite ignite() {
...
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache() {
return ignite().cache("myEntitycache");
}
MyDao
@Repository
public class MyDao {
@Autowired
private IgniteCache<Long, MyEntity> myEntityCache;
...
}
In principle Spring performs the bean setup in few phases as explained in chapter 1.3.2. Instantiating Beans docs:
Bean definition discovery - resources like
@Configuration
classes orXML
files are scanned and bean signatures are collected.Eager beans instantiation e.g. singletons - from the definitions collected in point 1 while resolving dependencies between definitions. That's why there is no explicit bean instantiation order as the process is driven from dependencies.
Lazy beans instantiation e.g.
@Lazy
annotated - when the context is already up, this beans will be constructed only when accessed from code.
1
I think this is right - the client is asking for aIgnite<Long,MyEntity>
but the configuration defines aIgniteCache<Long, MyEntity>
- which seems like a different type ...
– moilejter
Nov 11 at 23:41
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
add a comment |
This means that you don't have a bean of Ignite<Long,MyEntity>
type in your context. Moreover springContext
bean seems redundant, it's not used by igniteInstance
bean. As pointed out by moilejter it probably should be:
IgniteConfig
@Bean
public Ignite ignite() {
...
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache() {
return ignite().cache("myEntitycache");
}
MyDao
@Repository
public class MyDao {
@Autowired
private IgniteCache<Long, MyEntity> myEntityCache;
...
}
In principle Spring performs the bean setup in few phases as explained in chapter 1.3.2. Instantiating Beans docs:
Bean definition discovery - resources like
@Configuration
classes orXML
files are scanned and bean signatures are collected.Eager beans instantiation e.g. singletons - from the definitions collected in point 1 while resolving dependencies between definitions. That's why there is no explicit bean instantiation order as the process is driven from dependencies.
Lazy beans instantiation e.g.
@Lazy
annotated - when the context is already up, this beans will be constructed only when accessed from code.
This means that you don't have a bean of Ignite<Long,MyEntity>
type in your context. Moreover springContext
bean seems redundant, it's not used by igniteInstance
bean. As pointed out by moilejter it probably should be:
IgniteConfig
@Bean
public Ignite ignite() {
...
}
@Bean
public IgniteCache<Long, MyEntity> myEntityCache() {
return ignite().cache("myEntitycache");
}
MyDao
@Repository
public class MyDao {
@Autowired
private IgniteCache<Long, MyEntity> myEntityCache;
...
}
In principle Spring performs the bean setup in few phases as explained in chapter 1.3.2. Instantiating Beans docs:
Bean definition discovery - resources like
@Configuration
classes orXML
files are scanned and bean signatures are collected.Eager beans instantiation e.g. singletons - from the definitions collected in point 1 while resolving dependencies between definitions. That's why there is no explicit bean instantiation order as the process is driven from dependencies.
Lazy beans instantiation e.g.
@Lazy
annotated - when the context is already up, this beans will be constructed only when accessed from code.
edited Nov 11 at 23:47
answered Nov 11 at 23:30
Karol Dowbecki
16.4k82849
16.4k82849
1
I think this is right - the client is asking for aIgnite<Long,MyEntity>
but the configuration defines aIgniteCache<Long, MyEntity>
- which seems like a different type ...
– moilejter
Nov 11 at 23:41
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
add a comment |
1
I think this is right - the client is asking for aIgnite<Long,MyEntity>
but the configuration defines aIgniteCache<Long, MyEntity>
- which seems like a different type ...
– moilejter
Nov 11 at 23:41
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
1
1
I think this is right - the client is asking for a
Ignite<Long,MyEntity>
but the configuration defines a IgniteCache<Long, MyEntity>
- which seems like a different type ...– moilejter
Nov 11 at 23:41
I think this is right - the client is asking for a
Ignite<Long,MyEntity>
but the configuration defines a IgniteCache<Long, MyEntity>
- which seems like a different type ...– moilejter
Nov 11 at 23:41
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@moilejter you are most likely right, well spotted
– Karol Dowbecki
Nov 11 at 23:43
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
@Karol Dowbecki: I still have the same exception : Field myEntityCache com.demo.dao.MyDao required a bean of type 'org.apache.ignite.IgniteCache' that could not be found. And if i comment the dependency of IgniteCache in MyDao.class, Spring start and load it. So let say that the configuration of IgniteConfig.class must be loaded in the first then Appconfig.class can be loaded
– TinyOS
Nov 12 at 12:38
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
I made a mistake: In my Dao :private Ignite<String,MyEntity> myEntityCache; but in the configuration class i hade private Ignite<Long,MyEntity> myEntityCache; so not the same type (String vs Long) and that's why spring can't find the Bean igniteCache<String,...> Problem resolved
– TinyOS
Nov 12 at 12:53
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254191%2fwhy-spring-boot-does-not-load-beans-configuration-in-order%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Instead of taking them as a parameter, try callling igniteInstance() in myEntityCache(), and remove the parameter from igniteInstance() (as it doesn't seem to need the SpringContext for anything.. Spring usually finds all possible beans first, before creating any - so order of declaration should not matter... (I think that, as long as you have no cycles, it will order them as needed...).
– moilejter
Nov 11 at 23:24