Hi Val, I was unable to make Ignite work as a JCache provider (even thought it is possible to pass properties to the getCacheManager method, those properties are discarded by Ignite's Cache Manager, so there is no way to set the class loader to be used by ignite), however I did have success instead using it normally (good thing an Ignite Cache is a JCache cache). In order to keep using the MANIFEST dependencies/JBoss module paradigm I had to set the classloader in the InginiteConfiguration(setClassLoader) class using the classloader that loaded the code that starts ignite (Thread.currentThread().getContextClassLoader()).
And indeed you are correct that a solution is to place the ignite libraries in the EAR's lib folder as they can see the EJB's module code (by default in JBoss EAP 6+, the isolation among modules in an EAR is set to false, which means all modules can see each other, well, EJB/LIB/WAR modules can see LIBs and EJBs but WAR code can only be seen by WAR code) but I was trying to use the MANIFEST dependencies/jboss module approach. Thanks - Juan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Help-with-integrating-Ignite-as-JCache-with-JBoss-EAP-6-4-tp2134p2137.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
