root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 15 Packages Projects Releases Wiki Activity

Polish doc 

Closes gh-3344
This commit is contained in:
izeye 2015-06-28 21:46:30 +09:00 committed by Stephane Nicoll
parent a990cc1878
commit 4bc7919e04
2 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
View File

@ -530,10 +530,10 @@ under the `org.springframework.boot` domain.
[[production-ready-custom-mbean-names]] [[production-ready-custom-mbean-names]]
=== Customizing MBean names === Customizing MBean names
The name of the MBean is usually generated from the `id` of the endpoint. For example The name of the MBean is usually generated from the `id` of the endpoint. For example
the `health` endpoint is exposed as `org.springframework.boot/Endpoint/HealthEndpoint`. the `health` endpoint is exposed as `org.springframework.boot/Endpoint/healthEndpoint`.
If your application contains more than one Spring `ApplicationContext` you may find that If your application contains more than one Spring `ApplicationContext` you may find that
names clash. To solve this problem you can set the `endpoints.jmx.uniqueNames` property names clash. To solve this problem you can set the `endpoints.jmx.unique-names` property
to `true` so that MBean names are always unique. to `true` so that MBean names are always unique.
You can also customize the JMX domain under which endpoints are exposed. Here is an You can also customize the JMX domain under which endpoints are exposed. Here is an
@ -542,7 +542,7 @@ example `application.properties`:
[source,properties,indent=0] [source,properties,indent=0]
---- ----
endpoints.jmx.domain=myapp endpoints.jmx.domain=myapp
endpoints.jmx.uniqueNames=true endpoints.jmx.unique-names=true
---- ----
@ -605,8 +605,8 @@ If you are using Jolokia but you don't want Spring Boot to configure it, simply
[[production-ready-remote-shell]] [[production-ready-remote-shell]]
== Monitoring and management using a remote shell == Monitoring and management using a remote shell
Spring Boot supports an integrated Java shell called '`CRaSH`'. You can use CRaSH to Spring Boot supports an integrated Java shell called '`CRaSH`'. You can use CRaSH to
`ssh` or `telnet` into your running application. To enable remote shell support add a `ssh` or `telnet` into your running application. To enable remote shell support, add
dependency to `spring-boot-starter-remote-shell`: the following dependency to your project:
[source,xml,indent=0] [source,xml,indent=0]
---- ----
@ -683,15 +683,16 @@ for details). By default Spring Boot will search for commands in the following l
TIP: You can change the search path by settings a `shell.command-path-patterns` property. TIP: You can change the search path by settings a `shell.command-path-patterns` property.
Here is a simple '`hello world`' command that could be loaded from Here is a simple '`hello`' command that could be loaded from
`src/main/resources/commands/hello.groovy` `src/main/resources/commands/hello.groovy`
[source,groovy,indent=0] [source,groovy,indent=0]
---- ----
package commands package commands
import org.crsh.cli.Usage
import org.crsh.cli.Command import org.crsh.cli.Command
import org.crsh.cli.Usage
import org.crsh.command.InvocationContext
class hello { class hello {

4
spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
View File

@ -802,7 +802,7 @@ on the classpath change. This can be a useful feature when working in an IDE as
a very fast feedback loop for code changes. By default, any entry on the classpath that a very fast feedback loop for code changes. By default, any entry on the classpath that
points to a folder will be monitored for changes. points to a folder will be monitored for changes.
TIP: Automatic restart work very well when used with LiveReload. TIP: Automatic restart works very well when used with LiveReload.
<<using-boot-devtools-livereload,See below>> for details. <<using-boot-devtools-livereload,See below>> for details.
.Restart vs Reload .Restart vs Reload
@ -828,7 +828,7 @@ commercially supported.
==== Excluding resources ==== Excluding resources
Certain resources don't necessarily need to trigger a restart when they are changed. For Certain resources don't necessarily need to trigger a restart when they are changed. For
example, Thymeleaf templates can just be edited in-place. By default changing resources example, Thymeleaf templates can just be edited in-place. By default changing resources
in `/META-INF/maven`, ``/META-INF/resources` ,`/resources` ,`/static` ,`/public` or in `/META-INF/maven`, `/META-INF/resources` ,`/resources` ,`/static` ,`/public` or
`/templates` will not trigger a restart. If you want to customize these exclusions you `/templates` will not trigger a restart. If you want to customize these exclusions you
can use the `spring.devtools.restart.exclude` property. For example, to exclude only can use the `spring.devtools.restart.exclude` property. For example, to exclude only
`/static` and `/public` you would set the following: `/static` and `/public` you would set the following: