[
https://issues.apache.org/jira/browse/GEODE-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032683#comment-17032683
]
ASF subversion and git services commented on GEODE-7752:
--------------------------------------------------------
Commit 7028f601680fee3f57cbdff63951128d7180ca13 in geode's branch
refs/heads/mass-test-run from Udo Kohlmeyer
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7028f60 ]
GEODE-7752: Removed the current optionality on the
ClusterManagementServiceBuilder. (#4650)
The Transport is not responsible to set the ConnectionConfig.
> 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
> Fix For: 1.12.0, 1.13.0
>
> Time Spent: 2h 40m
> 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)
