SpringCloud/spring-cloud-openfeign
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Change DiscoveryClient->EurekaClient in docs

Browse Source
This commit is contained in:
Dave Syer
2015-09-30 11:34:28 +01:00
parent 17dc4f6f55
commit 3ef58cdc39
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/src/main/asciidoc/spring-cloud-netflix.adoc
View File

@@ -193,17 +193,17 @@ unique. In Cloudfoundry the `spring.application.instance_id` will be
populated automatically in a Spring Boot Actuator application, so the
random value will not be needed.
=== Using the DiscoveryClient
=== Using the EurekaClient
Once you have an app that is `@EnableEurekaClient` you can use it to
Once you have an app that is `@EnableDiscoveryClient` (or `@EnableEurekaClient`) you can use it to
discover service instances from the <<spring-cloud-eureka-server,
Eureka Server>>. One way to do that is to use the native
`com.netflix.discovery.DiscoveryClient` (as opposed to the Spring
`com.netflix.discovery.EurekaClient` (as opposed to the Spring
Cloud `DiscoveryClient`), e.g.
----
@Autowired
private DiscoveryClient discoveryClient;
private EurekaClient discoveryClient;
public String serviceUrl() {
InstanceInfo instance = discoveryClient.getNextServerFromEureka("STORES", false);
@@ -213,16 +213,16 @@ public String serviceUrl() {
[TIP]
====
Don't use the `DiscoveryClient` in `@PostConstruct` method or in a
Don't use the `EurekaClient` in `@PostConstruct` method or in a
`@Scheduled` method (or anywhere where the `ApplicationContext` might
not be started yet). It is initialized in a `SmartLifecycle` (with
`phase=0`) so the earliest you can rely on it being available is in
another `SmartLifecycle` with higher phase.
====
=== Alternatives to the native Netflix DiscoveryClient
=== Alternatives to the native Netflix EurekaClient
You don't have to use the raw Netflix `DiscoveryClient` and usually it
You don't have to use the raw Netflix `EurekaClient` and usually it
is more convenient to use it behind a wrapper of some sort. Spring
Cloud has support for <<spring-cloud-feign, Feign>> (a REST client
builder) and also <<spring-cloud-ribbon, Spring `RestTemplate`>> using