From c6152bdafa3c6a9ec738c0e444311c8e98d7a203 Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Thu, 9 Jun 2016 17:38:05 +0100 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud.html | 78 ++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 64 insertions(+), 14 deletions(-) diff --git a/spring-cloud.html b/spring-cloud.html index f71c8cfe..8ac200f1 100644 --- a/spring-cloud.html +++ b/spring-cloud.html @@ -536,6 +536,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b @@ -1506,7 +1507,7 @@ users. Example Maven configuration:

<parent>
     <groupId>org.springframework.boot</groupId>
     <artifactId>spring-boot-starter-parent</artifactId>
-    <version>1.2.3.RELEASE</version>
+    <version>1.3.5.RELEASE</version>
     <relativePath /> <!-- lookup parent from repository -->
 </parent>
 
@@ -1514,8 +1515,8 @@ users. Example Maven configuration:

     <dependencies>
         <dependency>
             <groupId>org.springframework.cloud</groupId>
-            <artifactId>spring-cloud-starter-parent</artifactId>
-            <version>1.0.1.RELEASE</version>
+            <artifactId>spring-cloud-dependencies</artifactId>
+            <version>Brixton.RELEASE</version>
             <type>pom</type>
             <scope>import</scope>
         </dependency>
@@ -1741,7 +1742,7 @@ Server? The strategy that governs this behaviour is the
 
{application} maps to "spring.application.name" on the client side;

 
 
  • 
-
    {profile} maps to "spring.active.profiles" on the client (comma separated list); and
    
+
    {profile} maps to "spring.profiles.active" on the client (comma separated list); and
    
 
    • 
 
  • 
 
    {label} which is a server side feature labelling a "versioned" set of config files.
    
@@ -3402,22 +3403,22 @@ normal Eureka functionality under /eureka/*.
    
 
 
 
    
-
    Due to Gradle’s dependency resolution rules and the lack of a parent bom feature, simply depending on spring-cloud-starter-eureka-server can cause failures on application startup. To remedy this the Spring dependency management plugin must be added and the Spring cloud starter parent bom must be imported like so:
    
+
    Due to Gradle’s dependency resolution rules and the lack of a parent bom feature, simply depending on spring-cloud-starter-eureka-server can cause failures on application startup. To remedy this the Spring Boot Gradle plugin must be added and the Spring cloud starter parent bom must be imported like so:
    
 
    
 
    
 
    build.gradle
    
 
    
 
    buildscript {
   dependencies {
-    classpath "io.spring.gradle:dependency-management-plugin:0.4.0.RELEASE"
+    classpath("org.springframework.boot:spring-boot-gradle-plugin:1.3.5.RELEASE")
   }
 }
 
-apply plugin: "io.spring.dependency-management"
+apply plugin: "spring-boot"
 
 dependencyManagement {
   imports {
-    mavenBom 'org.springframework.cloud:spring-cloud-starter-parent:1.0.0.RELEASE'
+    mavenBom "org.springframework.cloud:spring-cloud-dependencies:Brixton.RELEASE"
   }
 }
    
 
    
@@ -3708,18 +3709,30 @@ for details on the properties available.
    
 
    In this case, the cluster name from 4 services is pulled from their metadata map, and is expected to have values that include "SYSTEM" and "USER".
    
 
    
 
    
-
    To use the "default" cluster for all apps you need a string literal expression (with single quotes):
    
+
    To use the "default" cluster for all apps you need a string literal expression (with single quotes, and escaped with double quotes if it is in YAML as well):
    
 
    
 
    
 
    
 
    turbine:
   appConfig: customers,stores
-  clusterNameExpression: 'default'
    
+  clusterNameExpression: "'default'"

    • Spring Cloud provides a spring-cloud-starter-turbine that has all the dependencies you need to get a Turbine server running. Just create a Spring Boot application and annotate it with @EnableTurbine.

    +
    + + + + + +
    +
    Note
    +    		 +by default the native Netflix behaviour built into Turbine does not allow multiple processes per host, per cluster (the key to the instance id is the hostname). Spring Cloud generalizes this a bit, allowing the host and port to be used as the key, but only if you set the property turbine.combineHostPort=true +
    +

    Turbine Stream

    @@ -4507,7 +4520,7 @@ level, but "/myusers/**" matches hierarchically.

    The location of the backend can be specified as either a "serviceId" -(for a Eureka service) or a "url" (for a physical location), e.g.

    +(for a service from discovery) or a "url" (for a physical location), e.g.

    application.yml
    @@ -4700,6 +4713,30 @@ might add these headers too, and we want the values from the proxy.

    +

    The Routes Endpoint

    +
    +

    If you are using @EnableZuulProxy with tha Spring Boot Actuator you +will enable (by default) an additional endpoint, available via HTTP as +/routes. A GET to this endpoint will return a list of the mapped +routes. A POST will force a refresh of the existing routes (e.g. in +case there have been changes in the service catalog).

    +
    +
    + + + + + +
    +
    Note
    +    		 +the routes should respond automatically to changes in the +service catalog, but the POST to /routes is a way to force the change +to happen immediately. +
    +
    +
    +

    Strangulation Patterns and Local Forwards

    A common pattern when migrating an existing application or API is to @@ -6298,7 +6335,7 @@ spring.cloud.stream.bindings.output.binder=rabbit

    -

    Connecting to Multiple Systems

    +

    Connecting to Multiple Systems

    By default, binders share the application’s Spring Boot auto-configuration, so that one instance of each binder found on the classpath will be created. If your application should connect to more than one broker of the same type, you can specify multiple binder configurations, each with different environment settings.

    @@ -6472,6 +6509,19 @@ If set, only listed destinations can be bound.

    The default binder to use, if multiple binders are configured. See Multiple Binders on the Classpath.

    +
    +

    Default: empty.

    +
    +
    +
    spring.cloud.stream.overrideCloudConnectors
    +
    +

    This property is only applicable when the cloud profile is active and Spring Cloud Connectors are provided with the application. +If the property is false (the default), the binder will detect a suitable bound service (e.g. a RabbitMQ service bound in Cloud Foundry for the RabbitMQ binder) and will use it for creating connections (usually via Spring Cloud Connectors). +When set to true, this property instructs binders to completely ignore the bound services and rely on Spring Boot properties (e.g. relying on the spring.rabbitmq.* properties provided in the environment for the RabbitMQ binder). +The typical usage of this property is to be nested in a customized environment when connecting to multiple systems.

    +
    +

    Default: false.

    +
    @@ -13024,7 +13074,7 @@ created during auto-configuration.