So the CacheManager.getCache(String, Class, Class) is not supported then?
Thanks - J
> On 03 Jan, 2017, at 9:05 AM, vkulichenko
> wrote:
>
> Can you show the trace?
>
> -Val
>
>
>
> --
> View this message in context:
>
public class Test {
public static void main(String[] args) throws IOException {
CacheManager cacheManager =
Caching.getCachingProvider().getCacheManager(new
ClassPathResource("ignite-config-simple.xml").getURI(), null);
Cache cache =
Hi Val,
Thanks for the reply. So if I understand correctly, if a cache is defined to be
transactional, all accesses to the cache (either a put, get, size, clear, etc.)
have to be within the context of a transaction?
Thanks - J
> On 22 Jul, 2016, at 2:45 PM, vkulichenko
The four nodes are located on 4 different machines, 2 of each are located on a
different physical location.
Thanks - J
> On 21 Jul, 2016, at 8:58 PM, vkulichenko
> wrote:
>
> Hi,
>
> Are G1 and G2 two different physical machines and you start two nodes on
>
Hello Val,
Thank you for your prompt reply.
After responding to another issue you replied (Help with Integrating Ignite…
with JBoss…) I don’t know how easy would be to describe an IgniteConfiguration
object as a JSON string. As you mentioned in that reply, there are many
factories, SPIs,