zhengyangyong commented on a change in pull request #37: update
question-and-answer translation
URL:
https://github.com/apache/incubator-servicecomb-docs/pull/37#discussion_r211163870
##########
File path: java-chassis-reference/en_US/question-and-answer/question_answer.md
##########
@@ -197,79 +196,79 @@ public String sayHello(@RequestBody Person person){
}
```
-# 问题描述： body Model部分暴露
+# Problem: Partial exposure of body Model
-** 解决方法：**
+** Solution:**
-一个接口对应的body对象中，可能有一些属性是内部的，不想开放出去，生成schema的时候不要带出去，使用：
+In the body object corresponding to an interface, there may be some attributes
that are internal. Do not want to open it. Do not bring it out when generating
the schema. Use:
```java
@ApiModelProperty(hidden = true)
```
-# 问题描述：框架获取远端consumer的地址
+# Problem: The framework obtains the address of the remote consumer
-** 解决方法：**
+** Solution:**
-如果使用http rest方式（使用transport-rest-vertx依赖）可以用下面这种方式获取：
+If you use the http rest method (using the transport-rest-vertx dependency)
you can get it in the following way:
```java
HttpServletRequest request = (HttpServletRequest)
invocation.getHandlerContext().get(RestConst.REST_REQUEST);
String host = request.getRemoteHost();
```
-实际场景是拿最外层的地址，所以应该是LB传入到edgeservice，edgeService再放到context外下传递。
+The actual scene is to take the external address, so it should be LB passed to
edgeservice, and edgeService is then passed to the context and passed.
-# 问题描述：对handler描述
+# Problem: Description of the handler
-** 解决方法：**
+** Solution:**
-consumer默认的handler是simpleLB，没有配置的时候handler链会使用这个，如果配置了handler，里面一定要包含lb的handler，否则调用报错，需要在文档里面进行说明。
+Consumer default handler is simpleLB, and the handler chain will use this when
there is no configuration, if the handler is configured, it must contain the lb
handler. Otherwise the call error, need to be described in the document.
-# 问题描述：netty版本问题
+# Problem: Netty version problem
-** 解决方法：**
+** Solution:**
-netty3和netty4是完全不同的三方件，因为坐标跟package都不相同，所以可以共存，但是要注意小版本问题，小版本必须使用的版本。
+Netty3 and netty4 are completely different tripartites because the coordinates
are not the same as the package, so they can coexist, but pay attention to the
minor version problem, the version that the small version must use.
-# 问题描述：服务超时设置
+# Problem: Service Timeout Settings
-** 解决方法：**
+** Solution:**
-在微服务描述文件（microservice.yaml）中添加如下配置：
+Add the following configuration to the microservice description file
(microservice.yaml):
```
servicecomb:
request:
timeout: 30000
```
-# 问题描述：服务治理的处理链顺序是否有要求？
+# Problem: Is there a requirement for the processing chain of service
governance?
Review comment:
这个翻译不对，是对顺序是否有要求，不是对治理链有要求
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
