[ https://issues.apache.org/jira/browse/GEODE-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031149#comment-17031149 ]
ASF subversion and git services commented on GEODE-7752: -------------------------------------------------------- Commit 65ccf4540bb164e10988b7b48ecaae64b6b6e777 in geode's branch refs/heads/revert-4650-feature/GEODE-7752 from Udo Kohlmeyer [ https://gitbox.apache.org/repos/asf?p=geode.git;h=65ccf45 ] Revert "GEODE-7752: Removed the current optionality on the ClusterManagementServiceBuilder. (#4650)" This reverts commit 7028f601680fee3f57cbdff63951128d7180ca13. > Update ConfigurationServiceBuilder to be more intuitive > ------------------------------------------------------- > > Key: GEODE-7752 > URL: https://issues.apache.org/jira/browse/GEODE-7752 > Project: Geode > Issue Type: Improvement > Components: configuration > Reporter: Udo Kohlmeyer > Assignee: Udo Kohlmeyer > Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > With the introduction of ClusterManagementServiceBuilder, an inadvertent > confusing configuration manner was introduced. > In the Builder pattern, the setter methods are optional and required fields > are either added on the constructor or build method. > The current ClusterManangementServiceBuilder introduced the notion of > required optionality. Where you had to pick at least one of the setters. > To fix this, I removed `setConnectionConfig` which is really only required > for the Transport and removed that option. -- This message was sent by Atlassian Jira (v8.3.4#803005)