When SDG Annotation config is used to configure and bootstrap an Apache Geode server, automatically register the Administrative Functions [DATAGEODE-76]#124
Currently, when a user is using the client-side @EnableClusterConfiguration annotation to push client-side Apache Geode schema object definitions to the server without HTTP enabled (i.e. useHttp attribute set to false, the default), the user must configure/bootstrap their Apache Geode servers with Spring Boot/SDG and manually register the administrative Functions required by SDG to implement the cluster configuration push from the client without HTTP enabled, for example, where the client cluster configuration is configure as this.
When a user is using SDG's new Annotation-based configuration to configure and bootstrap an Apache Geode (cache) server, these internal, "administrative" Functions should automatically be registered, particularly since {{useHttp} is disabled by default.
John Blum opened DATAGEODE-76 and commented
Currently, when a user is using the client-side
@EnableClusterConfiguration
annotation to push client-side Apache Geode schema object definitions to the server without HTTP enabled (i.e.useHttp
attribute set to false, the default), the user must configure/bootstrap their Apache Geode servers with Spring Boot/SDG and manually register the administrative Functions required by SDG to implement the cluster configuration push from the client without HTTP enabled, for example, where the client cluster configuration is configure as this.When a user is using SDG's new Annotation-based configuration to configure and bootstrap an Apache Geode (cache) server, these internal, "administrative" Functions should automatically be registered, particularly since {{useHttp} is disabled by default.
Referenced from: commits 8ede35f, be32170
Backported to: 2.0.3 (Kay SR3)
The text was updated successfully, but these errors were encountered: