Using java chassis in spring boot dir translation (#40)
diff --git a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-between-java-web.md b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-between-java-web.md
index 180d66e..b6dc562 100644
--- a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-between-java-web.md
+++ b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-between-java-web.md
@@ -1,2 +1 @@
-两种开发方式都会启用java chassis的全量功能，JAVA应用方式运行于独立的HTTP服务器（基于vert.x构建）上，性能上存在很大的优势。Web开发方式运行于Tomcat或者其他内置的Web服务器之上，作为一个Servlet接收请求，因此在开发过程中，可以使用Web容器提供的一些功能，比如提供页面服务，使用Filter等。当应用只需要提供REST服务，并且对性能要求很高的场景，建议使用JAVA应用方式。
-
+Both development methods will enable the full functionality of the java chassis. The JAVA application mode runs on a separate HTTP server (based on vert.x), which has great advantages in performance. The web development method runs on Tomcat or other built-in web servers and receives requests as a servlet. Therefore, during the development process, you can use some functions provided by the web container, such as providing page services and using Filter. When the application only needs to provide REST services, and performance requirements are high, it is recommended to use a JAVA application mode.
diff --git a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-spring-mvc.md b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-spring-mvc.md
index a0e9c13..97e31d9 100644
--- a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-spring-mvc.md
+++ b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/diff-spring-mvc.md
@@ -1,73 +1,73 @@
-java chassis支持使用Spring MVC提供的标签\(org.springframework.web.bind.annotation\)来声明REST接口，但是两者是独立的实现，而且有不一样的设计目标。java chassis的目标是提供跨语言、支持多通信协议的框架，因此去掉了Spring MVC中一些对跨语言支持不是很好的特性，也不支持特定运行框架强相关的特性，比如直接访问Servlet协议定义的HttpServletRequest。下面是一些显著的差别。
-* 服务声明方式
+Java chassis supports the use of the label \(org.springframework.web.bind.annotation\) provided by Spring MVC to declare the REST interface, but the two are independent implementations and have different design goals. The goal of the java chassis is to provide a cross-language framework that supports multiple communication protocols. Therefore, some features of Spring MVC that are not very good for cross-language support are removed, and features that are strongly related to a specific running framework are not supported, such as direct access to the Servlet protocol definition. HttpServletRequest. Here are some notable differences.
-Spring MVC使用@RestController声明服务，而java chassis使用@RestSchema声明服务，并且需要显示的使用@RequestMapping声明服务路径，以区分该服务是采用Spring MVC的标签还是使用JAX RS的标签。
+* Service declaration method
+
+Spring MVC uses @RestController to declare the service, and java chassis uses @RestSchema to declare the service and needs to display the service path using @RequestMapping to distinguish whether the service uses Spring MVC Annotations or JAX RS Annotations.
```
@RestSchema(schemaId = "hello")
@RequestMapping(path = "/")
```
-Schema是java chassis的服务契约，是服务运行时的基础，服务治理、编解码等都基于契约进行。在跨语言的场景，契约也定义了不同语言能够同时理解的部分。
+The schema is the service contract of java chassis, which is the basis of service runtime. Service management, codec and so on are all based on contract. In a cross-language scenario, the contract also defines the parts of the language that can be understood simultaneously.
-* 数据类型支持
+* Data type support
-采用Spring MVC，可以在服务定义中使用多种数据类型，只要这种数据类型能够被json序列化和反序列化。比如：
+With Spring MVC, you can use multiple data types in a service definition as long as it can be serialized and deserialized by json. Such as:
```
-// 抽象类型
-public void postData(@RequestBody Object data)
-// 接口定义
-public void postData(@RequestBody IPerson interfaceData)
-// 没指定类型的泛型
-public void postData(@RequestBody Map rawData)
-// 具体协议相关的类型
-public void postData(HttpServletRequest rquest)
+// abstract type
+Public void postData(@RequestBody Object data)
+// Interface definition
+Public void postData(@RequestBody IPerson interfaceData)
+// Generics tpye without specified type
+Public void postData(@RequestBody Map rawData)
+// specific protocol related types
+Public void postData(HttpServletRequest request)
```
-上面的类型在java chassis都不提供支持。因为java chassis会根据接口定义生成契约，从上面的接口定义，如果不结合实际的实现代码或者额外的开发文档说明，无法直接生成契约。也就是站在浏览器的REST视角，不知道如何在body里面构造消息内容。
+The above types are not supported in the java chassis. Because java chassis will generate contracts according to the interface definition, from the above interface definition, if you do not combine the actual implementation code or additional development documentation, you can not directly generate the contract. That is, standing in the REST perspective of the browser, I don't know how to construct the message content in the body.
-为了支持快速开发，java chassis的数据类型限制也在不停的扩充，比如支持HttpServletRequest，但是实际在使用的时候，他们与WEB服务器的语义是不一样的，比如不能直接操作流。因此建议开发者在的使用场景下，尽可能使用契约能够描述的类型，让代码阅读性更好。
+To support rapid development, the data type restrictions of java chassis are also constantly expanding, such as support for HttpServletRequest, but when they are used, they are different from the semantics of the WEB server, such as the inability to directly manipulate the stream. Therefore, it is recommended that the developer use the type of contract that can be described as much as possible in the usage scenario so that the code is more readable.
-java chassis在数据类型的支持方面的更多说明，请参考"支持的数据类型"章节。
+For more information on java chassis support for data types, please refer to the "Supported Data Types" section.
-* 常用标签支持
+* Common Annotation Support
-下面是java chassis对于Spring MVC常用标签的支持情况。
+The following is the java chassis support for Spring MVC common annotation.
-| 标签名称 | 是否支持 | 说明 |
+| Tag Name | Support | Description |
| :--- | :--- | :--- |
-| RequestMapping | 是 | |
-| GetMapping | 是 | |
-| PutMapping | 是 | |
-| PostMapping | 是 | |
-| DeleteMapping | 是 | |
-| PatchMapping | 是 | |
-| RequestParam | 是 | |
-| CookieValue | 是 | |
-| PathVariable | 是 | |
-| RequestHeader | 是 | |
-| RequestBody | 是 | 目前支持application/json，plain/text |
-| RequestPart | 是 | 用于文件上传的场景，对应的标签还有Part、MultipartFile |
-| ResponseBody | 否 | 返回值缺省都是在body返回 |
-| ResponseStatus | 否 | 可以通过ApiResponse指定返回的错误码 |
-| RequestAttribute | 否 | Servlet协议相关的标签 |
-| SessionAttribute | 否 | Servlet协议相关的标签 |
-| MatrixVariable | 否 | |
-| ModelAttribute | 否 | |
-| ControllerAdvice | 否 | |
-| CrossOrigin | 否 | |
-| ExceptionHandler | 否 | |
-| InitBinder | 否 | |
+| RequestMapping | Yes | |
+| GetMapping | Yes | |
+| PutMapping | Yes | |
+| PostMapping | Yes | |
+| DeleteMapping | Yes | |
+| PatchMapping | Yes | |
+| RequestParam | Yes | |
+| CookieValue | Yes | |
+| PathVariable | Yes | |
+| RequestHeader | Yes | |
+RequestBody | Yes | Currently supports application/json,plain/text |
+RequestPart | Yes | For file upload scenarios, the corresponding tags are Part, MultipartFile |
+| ResponseBody | No | The return value defaults to the body return |
+| ResponseStatus | No | The error code returned can be specified by ApiResponse |
+RequestAttribute | No | Servlet Protocol Related Tags |
+SessionAttribute | No | Servlet Protocol Related Tags |
+| MatrixVariable | No | |
+| ModelAttribute | No | |
+| ControllerAdvice | No | |
+| CrossOrigin | No | |
+| ExceptionHandler | No | |
+| InitBinder | No | |
-* 其他
+* Other
-不支持在GET方法中使用POJO对象进行参数映射
+Using POJO objects for parameter mapping in GET methods is not supported.
-比如：public void getOperation\(Person p\)
+For example: public void getOperation\(Person p\)
-不支持在GET方法中使用Map映射所有可能的参数
+Do not support the use of Map mapping in the GET method for all possible parameters.
-比如：public void getOperation\(Map<String,String> p\)
-
+For example: public void getOperation\(Map<String,String> p\)
diff --git a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/java-application.md b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/java-application.md
index 7b09654..f145f57 100644
--- a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/java-application.md
+++ b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/java-application.md
@@ -1,12 +1,12 @@
-使用JAVA方式集成，为Spring Boot应用增加了一个高效的HTTP服务器和REST开发框架。这种方式集成非常简单。只需要在项目中引入相关依赖，并且使用@EnableServiceComb标签即可。
+Using JAVA integration, an efficient HTTP server and REST development framework has been added for Spring Boot applications. This way of integration is very simple. Just introduce the relevant dependencies into the project and use the @EnableServiceComb annotation.
-本项目[代码示例](https://github.com/huaweicse/servicecomb-java-chassis-samples/tree/master/spring-boot-simple)
+This project [code example] (https://github.com/huaweicse/servicecomb-java-chassis-samples/tree/master/spring-boot-simple)
-* 引入依赖
+* Introducing dependencies
-依赖关系中增加spring-boot-starter-provider，即可引入java chassis的核心功能。引入hibernate-validator的目的是spring boot会检测validation-api的实现类，检测不到会无法启动。
+Add the spring-boot-starter-provider to the dependency to introduce the core functions of the java chassis. The purpose of introducing hibernate-validator is that spring boot will detect the implementation class of validation-api, and it will not start if it is not detected.
```
<dependencyManagement>
@@ -38,10 +38,9 @@
```
+* Enable the core functions of java chassis
-* 启用java chassis的核心功能
-
-在启动类前面增加@EnableServiceComb即可。
+Add @EnableServiceComb in front of the startup class.
```
@SpringBootApplication
@@ -54,18 +53,17 @@
```
-
-通过以上配置，就可以完整使用java chassis提供的所有功能，使用java chassis开发REST服务，并开启各种治理功能。
+With the above configuration, you can fully use all the functions provided by the java chassis, use the java chassis to develop REST services, and open various governance functions.
-* 配置微服务
+* Configure microservices
-通过microservice.yaml文件可以定制微服务的信息，包括应用名称、微服务名称、监听的地址和端口等。
+The microservice.yaml file allows you to customize the microservice information, including the application id, microservice name, listener address and port.
-集成java chassis后，可以通过它的方式开发REST接口：
+After integrating java chassis, you can develop REST interface through it:
```
@RestSchema(schemaId = "hello")
@@ -80,7 +78,4 @@
-然后可以通过：http://localhost:9093/hello?name=world来访问。
-
-
-
+Then you can access it by http://localhost:9093/hello?name=world.
diff --git a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/web-application.md b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/web-application.md
index 74144ca..901446d 100644
--- a/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/web-application.md
+++ b/java-chassis-reference/en_US/using-java-chassis-in-spring-boot/web-application.md
@@ -1,29 +1,29 @@
-Web开发方式和JAVA应用方式的开发步骤基本类似。
+The development steps of the web development mode and the JAVA application mode are similar.
-本项目[代码示例](https://github.com/huaweicse/servicecomb-java-chassis-samples/tree/master/spring-boot-web)
+This project [code example] (https://github.com/huaweicse/servicecomb-java-chassis-samples/tree/master/spring-boot-web)
-主要有如下区别：
+Mainly differences:
-* JAVA应用方式基于spring-boot-starter，而Web开发方式基于spring-boot-starter-web。
+* JAVA application is based on spring-boot-starter, and web development is based on spring-boot-starter-web.
-* JAVA应用方式依赖spring-boot-starter-provider，而Web开发方式依赖spring-boot-starter-transport。spring-boot-starter-web已经携带了hibernate-validator，不需要额外依赖。
+* JAVA application depends on spring-boot-starter-provider, while web development depends on spring-boot-starter-transport. Spring-boot-starter-web already carries hibernate-validator and does not require additional dependencies.
-* 在启动函数中，Web开发方式可以通过声明
+* In the startup function, the web development mode can be declared
+
```
@SpringBootApplication(exclude=DispatcherServletAutoConfiguration.class)
```
-来关闭org.springframework.web.servlet.DispatcherServlet，通过@EnableServiceComb会启用org.apache.servicecomb.transport.rest.servlet.RestServlet。虽然排除DispatcherServlet不是必须的，但是大多数场景一个微服务里面存在多个REST框架都不是很好的主意，会造成很多使用上的误解。
+To close org.springframework.web.servlet.DispatcherServlet, enable org.apache.servicecomb.transport.rest.servlet.RestServlet via @EnableServiceComb. Although it is not necessary to exclude the DispatcherServlet, it is not a good idea to have multiple REST frameworks in a microservice in most scenarios, which will cause much confusion in use.
-* 在microservice.yaml文件中通过配置项servicecomb.rest.servlet.urlPattern来指定RestServlet的URL根路径。并且配置项servicecomb.rest.address里面的监听端口，必须和tomcat监听的端口保持一致（默认是8080，可以通过application.yml中增加server.port修改）
+* Specify the URL root path of the RestServlet in the microservice.yaml file via the configuration item servicecomb.rest.servlet.urlPattern. And the listening port in the configuration item servicecomb.rest.address must be consistent with the port that the tomcat listens on (the default is 8080, which can be modified by adding server.port in application.yml)
-
-集成java chassis后，可以通过它的方式开发REST接口：
+After integrating java chassis, you can develop REST interface through it:
```
@RestSchema(schemaId = "hello")
@@ -36,15 +36,14 @@
}
```
-然后可以通过：http://localhost:9093/hello?name=world来访问。
+Then you can access it by http://localhost:9093/hello?name=world.
-可以看到使用的标签和Spring MVC大部分是一样的。但也有少量不一样的地方，比如：
+You can see that the tags used are mostly the same as Spring MVC. But there are also a few different places, such as:
-1. 通过RestSchema替换RestController
+1. Replace RestController with RestSchema
-2. 需要显示声明@RequestMapping
+2. Declare @RequestMapping explicitly.
-如果业务代码不是新开发，而是基于Spring MVC做的开发，现在java chassis基于做改造，还需要注意在禁用DispatcherServlet后，和其有关的功能特性将不再生效。
+If the business code is not a new development but based on the development of Spring MVC, now the java chassis is based on the transformation, but also need to pay attention to the disabling of the DispatcherServlet, and its related features will no longer take effect.
-在下面的章节，还会详细介绍在Spring MVC模式下两者的区别。
-
+In the following sections, about web JAVA application mode and web development mode, we'll introduce some details of the differences in Spring MVC mode.
\ No newline at end of file
diff --git a/java-chassis-reference/zh_CN/using-java-chassis-in-spring-boot/java-application.md b/java-chassis-reference/zh_CN/using-java-chassis-in-spring-boot/java-application.md
index 7b09654..1d6dd1d 100644
--- a/java-chassis-reference/zh_CN/using-java-chassis-in-spring-boot/java-application.md
+++ b/java-chassis-reference/zh_CN/using-java-chassis-in-spring-boot/java-application.md
@@ -1,4 +1,4 @@
-使用JAVA方式集成，为Spring Boot应用增加了一个高效的HTTP服务器和REST开发框架。这种方式集成非常简单。只需要在项目中引入相关依赖，并且使用@EnableServiceComb标签即可。
+使用JAVA方式集成，为Spring Boot应用增加了一个高效的HTTP服务器和REST开发框架。这种方式集成非常简单。只需要在项目中引入相关依赖，并且使用@EnableServiceComb注解即可。
本项目[代码示例](https://github.com/huaweicse/servicecomb-java-chassis-samples/tree/master/spring-boot-simple)
