Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixme 2.0 patch1 #1473

Merged
merged 9 commits into from
Nov 15, 2022
Merged

Fixme 2.0 patch1 #1473

merged 9 commits into from
Nov 15, 2022

Conversation

spencergibb
Copy link
Contributor

@spencergibb spencergibb commented Oct 31, 2022

Creates new EurekaServerHttpClientFactory

This is basically EurekaServerHttpClients, but as an interface. Various constructors changed from taking EurekaHttpClient to EurekaServerHttpClientFactory.

Adds TransportClientFactories as required parameter to DiscoveryClient.

Removes deprecated DiscoveryClient constructors.

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class Jersey3RemoteRegionClientFactory implements TransportClientFactory {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spencergibb spencergibb marked this pull request as ready for review November 3, 2022 18:19

public DiscoveryClient(ApplicationInfoManager applicationInfoManager, EurekaClientConfig config) {
this(applicationInfoManager, config, null);
@SuppressWarnings("rawtypes")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now TransportClientFactories is mandatory. This would break anyone who doesn't use SB cloud. Is there a way that we can construct a default TransportClientFactories for users and provide ctor option w/o TransportClientFactories? I know it's a major release, but I'm not sure how users would know about what to do to construct a TransportClientFactories?

Copy link
Contributor Author

@spencergibb spencergibb Nov 4, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not without merging jersey 3 modules into core and client. Spring cloud netflix will auto-configure the right thing. Right now there is no guice support, so until that happens no one can use it without spring cloud netflix anyway. If you do get guice support, then that would do the right thing. No one should be trying to construct a discovery client by hand.

EurekaServerIdentity identity = new EurekaServerIdentity(ip);*/
// FIXME 2.0
// discoveryApacheClient.addFilter(new EurekaIdentityHeaderFilter(identity));
EurekaServerIdentity identity = new EurekaServerIdentity(ip);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these lines still be here? There's no more FIXME 2.0 so I'm not sure.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, those are for the non-experimental client I still need to add back. If you look at the top of the comment block, there is a FIXME: 2.0 still

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants