Juan, I don't see how this will help you. IgnitionEx.loadConfigurations(springCfgUrl) still uses Spring to load configuration from the file.
I think the best way is to create IgniteConfiguration object, set class loader, start Ignite and create cache using Ignite API. If you then use only JCache APIs, switching to another provider will be very easy even if you don't use CacheManager. But note that not all Ignite features will be available in this case (like SQL queries, for example). -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Help-with-integrating-Ignite-as-JCache-with-JBoss-EAP-6-4-tp2134p2171.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
