You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by zshamrock <al...@gmail.com> on 2016/05/04 16:44:58 UTC

How rich is Spring support for Ignite configuration file

Does Spring configuration file used to configure ignite support property
placeholders ${} and getting the properties from file by using
<context:property-placeholder location="classpath:cache.properties"/>, as
well as expression language #{}?

In general what is supported by "Ignite" Spring and what is not.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-rich-is-Spring-support-for-Ignite-configuration-file-tp4774.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How rich is Spring support for Ignite configuration file

Posted by zshamrock <al...@gmail.com>.
You are right. It works. I might misconfigured my application yesterday.

Thank you.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-rich-is-Spring-support-for-Ignite-configuration-file-tp4774p4781.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How rich is Spring support for Ignite configuration file

Posted by vdpyatkov <vl...@gmail.com>.
Hello,

Yes, Ignite support full Spring configuration file. In my opinion, property
placeholder and Spel must work in all case like it is doing in Spring.
If you have example where it not so, please provide your source code.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-rich-is-Spring-support-for-Ignite-configuration-file-tp4774p4780.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.