Juan, Anton Vinogradov has identified the problem in cache manager and fixed it (one-liner fix) and will check tc today. If this does not break anything, we will include it into ignite-1.5 release which should be available early next week.
--Yakov 2015-12-08 18:18 GMT+03:00 juanavelez <[email protected]>: > That was the original approach but seeing how difficult it is to correctly > set the IgniteConfiguration object (either by using Properties as you > pointed out earlier in this thread because of Factories, SPIs, etc. or JSON > as stated in another thread), we realized we could not avoid using Spring > and hence the route of using IgnitionEx.loadConfigurations(springCfgUrl) > which I agree tightly couples us to a specific JCache implementation. > > We have already tested the approach and it seems to work at least for our > purposes. > > And yes, indeed we are bound by what the JCache API allows > Ignite/Hazelcast to expose which might not be the full features. > > BTW: We are very happy with Ignite, it has very strong features (we like > the most the seamless integration with JTA/XA!) which fit perfect our > intended purpose. Thank you for such a great product and your constant help. > > > Thanks - Juan > > > On Dec 7, 2015, at 2:25 PM, vkulichenko [via Apache Ignite Users] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=2178&i=0>> wrote: > > 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 > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-ignite-users.70518.x6.nabble.com/Help-with-integrating-Ignite-as-JCache-with-JBoss-EAP-6-4-tp2134p2171.html > To unsubscribe from Help with integrating Ignite(as JCache) with JBoss EAP > 6.4, click here. > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > > > ------------------------------ > View this message in context: Re: Help with integrating Ignite(as JCache) > with JBoss EAP 6.4 > <http://apache-ignite-users.70518.x6.nabble.com/Help-with-integrating-Ignite-as-JCache-with-JBoss-EAP-6-4-tp2134p2178.html> > Sent from the Apache Ignite Users mailing list archive > <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. >
