Improve CQ Auto-configuration by assessing the availability of a server or cluster first before enabling and auto-configuring CQ functionality.
This added capabilities relies on the new ClusterAwareConditions. Resolves gh-53.
This commit is contained in:
@@ -32,8 +32,8 @@ import org.springframework.data.gemfire.config.annotation.EnableClusterConfigura
|
||||
@Configuration
|
||||
@Conditional(ClusterAvailableConfiguration.ClusterAvailableCondition.class)
|
||||
@EnableClusterConfiguration(requireHttps = false, useHttp = true)
|
||||
class ClusterAvailableConfiguration {
|
||||
public class ClusterAvailableConfiguration {
|
||||
|
||||
static final class ClusterAvailableCondition extends ClusterAwareConfiguration.ClusterAwareCondition { }
|
||||
public static final class ClusterAvailableCondition extends ClusterAwareConfiguration.ClusterAwareCondition { }
|
||||
|
||||
}
|
||||
|
||||
@@ -97,7 +97,7 @@ public class ClusterNotAvailableConfiguration {
|
||||
return clientRegion;
|
||||
}
|
||||
|
||||
static final class CusterNotAvailableCondition extends ClusterAwareConfiguration.ClusterAwareCondition {
|
||||
public static final class CusterNotAvailableCondition extends ClusterAwareConfiguration.ClusterAwareCondition {
|
||||
|
||||
@Override
|
||||
public synchronized boolean matches(ConditionContext context, AnnotatedTypeMetadata metadata) {
|
||||
|
||||
Reference in New Issue
Block a user