We use a third party library to get data from an external gemfire cache cluster. We also connect to our own gemfire cache cluster. We use client cache to connect to our cluster and the third party library has its own client cache defined in its own application context.
The third party library does not use "spring data gemfire repository" functionality whereas we do. We are facing issues while querying our cache using the "Spring data gemfire repository" functionality depending upon the order in which the application context's gets loaded. If our context gets loaded first then everything works where if the third party gets loaded first then our query call fails though save works fine.
On debugging what I found was in the later case, the default-pool referred to in the query-service points to the third party cluster and hence does not have our regions.
Due to enterprise constraints we do not have control over the order in which the application context gets loaded. Is there any way we can customize the default pool being used so that even if the third party app context gets loaded we are still able to override the default pool to point to our locator pool rather than any other?
