Browse Source

Sync docs from 1.3.x to gh-pages

pull/507/head
buildmaster 7 years ago
parent
commit
a0d3d47409
  1. 3
      1.3.x/multi/multi__spring_cloud_context_application_context_services.html
  2. 3
      1.3.x/single/spring-cloud-commons.html
  3. 3
      1.3.x/spring-cloud-commons.xml

3
1.3.x/multi/multi__spring_cloud_context_application_context_services.html

@ -10,7 +10,8 @@ the box it is responsible for loading configuration properties from @@ -10,7 +10,8 @@ the box it is responsible for loading configuration properties from
the external sources, and also decrypting properties in the local
external configuration files. The two contexts share an <code class="literal">Environment</code>
which is the source of external properties for any Spring
application. Bootstrap properties are added with high precedence, so
application. Bootstrap properties (not <code class="literal">bootstrap.properties</code> but properties
that are loaded during the bootstrap phase) are added with high precedence, so
they cannot be overridden by local configuration, by default.</p><p>The bootstrap context uses a different convention for locating
external configuration than the main application context, so instead
of <code class="literal">application.yml</code> (or <code class="literal">.properties</code>) you use <code class="literal">bootstrap.yml</code>,

3
1.3.x/single/spring-cloud-commons.html

@ -10,7 +10,8 @@ the box it is responsible for loading configuration properties from @@ -10,7 +10,8 @@ the box it is responsible for loading configuration properties from
the external sources, and also decrypting properties in the local
external configuration files. The two contexts share an <code class="literal">Environment</code>
which is the source of external properties for any Spring
application. Bootstrap properties are added with high precedence, so
application. Bootstrap properties (not <code class="literal">bootstrap.properties</code> but properties
that are loaded during the bootstrap phase) are added with high precedence, so
they cannot be overridden by local configuration, by default.</p><p>The bootstrap context uses a different convention for locating
external configuration than the main application context, so instead
of <code class="literal">application.yml</code> (or <code class="literal">.properties</code>) you use <code class="literal">bootstrap.yml</code>,

3
1.3.x/spring-cloud-commons.xml

@ -42,7 +42,8 @@ the box it is responsible for loading configuration properties from @@ -42,7 +42,8 @@ the box it is responsible for loading configuration properties from
the external sources, and also decrypting properties in the local
external configuration files. The two contexts share an <literal>Environment</literal>
which is the source of external properties for any Spring
application. Bootstrap properties are added with high precedence, so
application. Bootstrap properties (not <literal>bootstrap.properties</literal> but properties
that are loaded during the bootstrap phase) are added with high precedence, so
they cannot be overridden by local configuration, by default.</simpara>
<simpara>The bootstrap context uses a different convention for locating
external configuration than the main application context, so instead

Loading…
Cancel
Save