In case someone else hits this, the issue is easily resolved by embedding
cachestore and datasource facotyr beans in the cache bean, instead of using
spring references:
Franck
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Client-requires-DataSource-bean
Thanks Val, that makes sense.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Client-requires-DataSource-bean-configuration-copy-tp15491p15576.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
. This will simplify the process.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Client-requires-DataSource-bean-configuration-copy-tp15491p15523.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
518.x6.nabble.com/Client-requires-DataSource-bean-configuration-copy-tp15491.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.