WillemJiang closed pull request #34: replace io.servicecomb to
org.apache.servicecomb
URL: https://github.com/apache/incubator-servicecomb-website/pull/34
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/_docs/cn/distributed-tracing.md b/_docs/cn/distributed-tracing.md
index efe81b1..3ecec28 100644
--- a/_docs/cn/distributed-tracing.md
+++ b/_docs/cn/distributed-tracing.md
@@ -20,7 +20,7 @@ last_modified_at: 2017-09-03T10:01:43-04:00
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-tracing-zipkin</artifactId>
</dependency>
```
@@ -39,7 +39,7 @@ last_modified_at: 2017-09-03T10:01:43-04:00
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul-zipkin</artifactId>
</dependency>
```
diff --git a/_docs/cn/flow-control.md b/_docs/cn/flow-control.md
index 5ac5c3c..d607b6a 100644
--- a/_docs/cn/flow-control.md
+++ b/_docs/cn/flow-control.md
@@ -20,7 +20,7 @@ last_modified_at: 2017-09-03T10:01:43-04:00
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-flowcontrol-qps</artifactId>
</dependency>
```
diff --git a/_docs/cn/quick-start-bmi.md b/_docs/cn/quick-start-bmi.md
index caca144..594e192 100644
--- a/_docs/cn/quick-start-bmi.md
+++ b/_docs/cn/quick-start-bmi.md
@@ -23,9 +23,9 @@ last_modified_at: 2017-09-04T10:01:43-04:00
<dependencyManagement>
<dependencies>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>0.5.0</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -81,7 +81,7 @@ public interface CalculatorEndpoint {
引入 **ServiceComb** 依赖：
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
</dependency>
```
@@ -153,15 +153,15 @@ public class CalculatorApplication {
引入依赖：
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-discovery</artifactId>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-servicecomb</artifactId>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul</artifactId>
</dependency>
```
diff --git a/_docs/cn/quick-start-dataconsistency.md
b/_docs/cn/quick-start-dataconsistency.md
index 372a9b0..d333859 100644
--- a/_docs/cn/quick-start-dataconsistency.md
+++ b/_docs/cn/quick-start-dataconsistency.md
@@ -417,7 +417,7 @@ last_modified_at: 2017-09-19T11:50:10-04:00
"sagaId": "2654fa50-71e2-4fc8-afc2-6a5e0d3dafe9",
"creationTime": "2017-09-20T00:31:15Z",
"type": "TransactionAbortedEvent",
- "contentJson": "{\"request\": {\"id\": \"request-payment\",
\"type\": \"rest\", \"parents\": [\"request-car\", \"request-flight\",
\"request-hotel\"], \"fallback\": {\"type\": \"NOP\"}, \"serviceName\":
\"payment-service\", \"transaction\": {\"path\": \"/payments\", \"method\":
\"post\", \"params\": {\"form\": {\"customerId\": \"mike\"}}},
\"compensation\": {\"path\": \"/payments\", \"method\": \"put\", \"params\":
{\"form\": {\"customerId\": \"mike\"}}, \"retries\": 3}}, \"response\":
{\"body\": \"{\\n \\\"body\\\":
\\\"io.servicecomb.saga.core.TransactionFailedException: The remote service
payment-service failed to serve the post request to /payments \\n\\tat
io.servicecomb.saga.discovery.service.center.ServiceCenterDiscoveryRestTransport.with(ServiceCenterDiscoveryRestTransport.java:81)\\n\\tat
io.servicecomb.saga.format.JacksonRestOperation.send(JacksonRestOperation.java:43)\\n\\tat
io.servicecomb.saga.format.JacksonRestTransaction.send(JacksonRestTransaction.java:24)\\n\\tat
io.servicecomb.saga.core.RequestProcessTask.commit(RequestProcessTask.java:45)\\n\\tat
io.servicecomb.saga.core.BackwardRecovery.apply(BackwardRecovery.java:33)\\n\\tat
io.servicecomb.saga.core.LoggingRecoveryPolicy.apply(LoggingRecoveryPolicy.java:38)\\n\\tat
io.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:110)\\n\\tat
io.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:94)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\\n\\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\\n\\tat
java.lang.Thread.run(Thread.java:748)\\nCaused by: InvocationException:
code=490;msg=CommonExceptionData [message=Cse Internal Bad Request]\\n\\tat
io.servicecomb.swagger.invocation.exception.ExceptionFactory.doCreate(ExceptionFactory.java:74)\\n\\tat
io.servicecomb.swagger.invocation.exception.ExceptionFactory.convertException(ExceptionFactory.java:119)\\n\\tat
io.servicecomb.swagger.invocation.exception.ExceptionFactory.convertConsumerException(ExceptionFactory.java:78)\\n\\tat
io.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:128)\\n\\tat
io.servicecomb.swagger.invocation.Response.createFail(Response.java:121)\\n\\tat
io.servicecomb.swagger.invocation.AsyncResponse.fail(AsyncResponse.java:41)\\n\\tat
io.servicecomb.transport.rest.client.http.VertxHttpMethod.lambda$doMethod$0(VertxHttpMethod.java:67)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleException(HttpClientRequestBase.java:110)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestImpl.handleException(HttpClientRequestImpl.java:50)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.timeout(HttpClientRequestBase.java:155)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleTimeout(HttpClientRequestBase.java:140)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.lambda$setTimeout$0(HttpClientRequestBase.java:100)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:782)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:753)\\n\\tat
io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:316)\\n\\tat
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418)\\n\\tat
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)\\n\\t...
1 more\\nCaused by: java.util.concurrent.TimeoutException: The timeout period
of 30000ms has been exceeded\\n\\t... 11 more\\n\\\"\\n}\"}}"
+ "contentJson": "{\"request\": {\"id\": \"request-payment\",
\"type\": \"rest\", \"parents\": [\"request-car\", \"request-flight\",
\"request-hotel\"], \"fallback\": {\"type\": \"NOP\"}, \"serviceName\":
\"payment-service\", \"transaction\": {\"path\": \"/payments\", \"method\":
\"post\", \"params\": {\"form\": {\"customerId\": \"mike\"}}},
\"compensation\": {\"path\": \"/payments\", \"method\": \"put\", \"params\":
{\"form\": {\"customerId\": \"mike\"}}, \"retries\": 3}}, \"response\":
{\"body\": \"{\\n \\\"body\\\":
\\\"org.apache.servicecomb.saga.core.TransactionFailedException: The remote
service payment-service failed to serve the post request to /payments \\n\\tat
org.apache.servicecomb.saga.discovery.service.center.ServiceCenterDiscoveryRestTransport.with(ServiceCenterDiscoveryRestTransport.java:81)\\n\\tat
org.apache.servicecomb.saga.format.JacksonRestOperation.send(JacksonRestOperation.java:43)\\n\\tat
org.apache.servicecomb.saga.format.JacksonRestTransaction.send(JacksonRestTransaction.java:24)\\n\\tat
org.apache.servicecomb.saga.core.RequestProcessTask.commit(RequestProcessTask.java:45)\\n\\tat
org.apache.servicecomb.saga.core.BackwardRecovery.apply(BackwardRecovery.java:33)\\n\\tat
org.apache.servicecomb.saga.core.LoggingRecoveryPolicy.apply(LoggingRecoveryPolicy.java:38)\\n\\tat
org.apache.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:110)\\n\\tat
org.apache.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:94)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\\n\\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\\n\\tat
java.lang.Thread.run(Thread.java:748)\\nCaused by: InvocationException:
code=490;msg=CommonExceptionData [message=Cse Internal Bad Request]\\n\\tat
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.doCreate(ExceptionFactory.java:74)\\n\\tat
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertException(ExceptionFactory.java:119)\\n\\tat
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertConsumerException(ExceptionFactory.java:78)\\n\\tat
org.apache.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:128)\\n\\tat
org.apache.servicecomb.swagger.invocation.Response.createFail(Response.java:121)\\n\\tat
org.apache.servicecomb.swagger.invocation.AsyncResponse.fail(AsyncResponse.java:41)\\n\\tat
org.apache.servicecomb.transport.rest.client.http.VertxHttpMethod.lambda$doMethod$0(VertxHttpMethod.java:67)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleException(HttpClientRequestBase.java:110)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestImpl.handleException(HttpClientRequestImpl.java:50)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.timeout(HttpClientRequestBase.java:155)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleTimeout(HttpClientRequestBase.java:140)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.lambda$setTimeout$0(HttpClientRequestBase.java:100)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:782)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:753)\\n\\tat
io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:316)\\n\\tat
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418)\\n\\tat
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)\\n\\t...
1 more\\nCaused by: java.util.concurrent.TimeoutException: The timeout period
of 30000ms has been exceeded\\n\\t... 11 more\\n\\\"\\n}\"}}"
},
{
"id": 20,
diff --git a/_docs/cn/service-management.md b/_docs/cn/service-management.md
index 924bc4d..236e94e 100644
--- a/_docs/cn/service-management.md
+++ b/_docs/cn/service-management.md
@@ -20,7 +20,7 @@ last_modified_at: 2017-09-03T10:01:43-04:00
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-bizkeeper</artifactId>
</dependency>
```
diff --git a/_docs/distributed-tracing.md b/_docs/distributed-tracing.md
index 91ace81..92d7b98 100644
--- a/_docs/distributed-tracing.md
+++ b/_docs/distributed-tracing.md
@@ -20,7 +20,7 @@ Walk through [Develop microservice application in
minutes](/docs/quick-start-bmi
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-tracing-zipkin</artifactId>
</dependency>
```
@@ -39,7 +39,7 @@ Walk through [Develop microservice application in
minutes](/docs/quick-start-bmi
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul-zipkin</artifactId>
</dependency>
```
diff --git a/_docs/flow-control.md b/_docs/flow-control.md
index bbf0f83..155537f 100644
--- a/_docs/flow-control.md
+++ b/_docs/flow-control.md
@@ -20,7 +20,7 @@ Walk through [Develop microservice application in
minutes](/docs/quick-start-bmi
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-flowcontrol-qps</artifactId>
</dependency>
```
diff --git a/_docs/quick-start-bmi.md b/_docs/quick-start-bmi.md
index 75f4700..fe62f12 100644
--- a/_docs/quick-start-bmi.md
+++ b/_docs/quick-start-bmi.md
@@ -23,9 +23,9 @@ Before we start, we need to add some common dependencies in
the parent project o
<dependencyManagement>
<dependencies>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>0.5.0</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -82,7 +82,7 @@ public interface CalculatorEndpoint {
Introduce ServiceComb dependency:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
</dependency>
```
@@ -153,15 +153,15 @@ The gateway service was implemented using the [Netflix
Zuul](https://github.com/
Introduce ServiceComb dependency:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-discovery</artifactId>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-servicecomb</artifactId>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul</artifactId>
</dependency>
```
diff --git a/_docs/quick-start-dataconsistency.md
b/_docs/quick-start-dataconsistency.md
index ab6112c..adc6397 100644
--- a/_docs/quick-start-dataconsistency.md
+++ b/_docs/quick-start-dataconsistency.md
@@ -418,7 +418,7 @@ Note, demo is in the
[ServiceComb-Saga](https://github.com/apache/incubator-serv
"sagaId": "2654fa50-71e2-4fc8-afc2-6a5e0d3dafe9",
"creationTime": "2017-09-20T00:31:15Z",
"type": "TransactionAbortedEvent",
- "contentJson": "{\"request\": {\"id\": \"request-payment\",
\"type\": \"rest\", \"parents\": [\"request-car\", \"request-flight\",
\"request-hotel\"], \"fallback\": {\"type\": \"NOP\"}, \"serviceName\":
\"payment-service\", \"transaction\": {\"path\": \"/payments\", \"method\":
\"post\", \"params\": {\"form\": {\"customerId\": \"mike\"}}},
\"compensation\": {\"path\": \"/payments\", \"method\": \"put\", \"params\":
{\"form\": {\"customerId\": \"mike\"}}, \"retries\": 3}}, \"response\":
{\"body\": \"{\\n \\\"body\\\":
\\\"io.servicecomb.saga.core.TransactionFailedException: The remote service
payment-service failed to serve the post request to /payments \\n\\tat
io.servicecomb.saga.discovery.service.center.ServiceCenterDiscoveryRestTransport.with(ServiceCenterDiscoveryRestTransport.java:81)\\n\\tat
io.servicecomb.saga.format.JacksonRestOperation.send(JacksonRestOperation.java:43)\\n\\tat
io.servicecomb.saga.format.JacksonRestTransaction.send(JacksonRestTransaction.java:24)\\n\\tat
io.servicecomb.saga.core.RequestProcessTask.commit(RequestProcessTask.java:45)\\n\\tat
io.servicecomb.saga.core.BackwardRecovery.apply(BackwardRecovery.java:33)\\n\\tat
io.servicecomb.saga.core.LoggingRecoveryPolicy.apply(LoggingRecoveryPolicy.java:38)\\n\\tat
io.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:110)\\n\\tat
io.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:94)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\\n\\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\\n\\tat
java.lang.Thread.run(Thread.java:748)\\nCaused by: InvocationException:
code=490;msg=CommonExceptionData [message=Cse Internal Bad Request]\\n\\tat
io.servicecomb.swagger.invocation.exception.ExceptionFactory.doCreate(ExceptionFactory.java:74)\\n\\tat
io.servicecomb.swagger.invocation.exception.ExceptionFactory.convertException(ExceptionFactory.java:119)\\n\\tat
io.servicecomb.swagger.invocation.exception.ExceptionFactory.convertConsumerException(ExceptionFactory.java:78)\\n\\tat
io.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:128)\\n\\tat
io.servicecomb.swagger.invocation.Response.createFail(Response.java:121)\\n\\tat
io.servicecomb.swagger.invocation.AsyncResponse.fail(AsyncResponse.java:41)\\n\\tat
io.servicecomb.transport.rest.client.http.VertxHttpMethod.lambda$doMethod$0(VertxHttpMethod.java:67)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleException(HttpClientRequestBase.java:110)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestImpl.handleException(HttpClientRequestImpl.java:50)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.timeout(HttpClientRequestBase.java:155)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleTimeout(HttpClientRequestBase.java:140)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.lambda$setTimeout$0(HttpClientRequestBase.java:100)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:782)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:753)\\n\\tat
io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:316)\\n\\tat
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418)\\n\\tat
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)\\n\\t...
1 more\\nCaused by: java.util.concurrent.TimeoutException: The timeout period
of 30000ms has been exceeded\\n\\t... 11 more\\n\\\"\\n}\"}}"
+ "contentJson": "{\"request\": {\"id\": \"request-payment\",
\"type\": \"rest\", \"parents\": [\"request-car\", \"request-flight\",
\"request-hotel\"], \"fallback\": {\"type\": \"NOP\"}, \"serviceName\":
\"payment-service\", \"transaction\": {\"path\": \"/payments\", \"method\":
\"post\", \"params\": {\"form\": {\"customerId\": \"mike\"}}},
\"compensation\": {\"path\": \"/payments\", \"method\": \"put\", \"params\":
{\"form\": {\"customerId\": \"mike\"}}, \"retries\": 3}}, \"response\":
{\"body\": \"{\\n \\\"body\\\":
\\\"org.apache.servicecomb.saga.core.TransactionFailedException: The remote
service payment-service failed to serve the post request to /payments \\n\\tat
org.apache.servicecomb.saga.discovery.service.center.ServiceCenterDiscoveryRestTransport.with(ServiceCenterDiscoveryRestTransport.java:81)\\n\\tat
org.apache.servicecomb.saga.format.JacksonRestOperation.send(JacksonRestOperation.java:43)\\n\\tat
org.apache.servicecomb.saga.format.JacksonRestTransaction.send(JacksonRestTransaction.java:24)\\n\\tat
org.apache.servicecomb.saga.core.RequestProcessTask.commit(RequestProcessTask.java:45)\\n\\tat
org.apache.servicecomb.saga.core.BackwardRecovery.apply(BackwardRecovery.java:33)\\n\\tat
org.apache.servicecomb.saga.core.LoggingRecoveryPolicy.apply(LoggingRecoveryPolicy.java:38)\\n\\tat
org.apache.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:110)\\n\\tat
org.apache.servicecomb.saga.core.TransactionTaskConsumer$OperationCallable.call(TransactionTaskConsumer.java:94)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\\n\\tat
java.util.concurrent.FutureTask.run(FutureTask.java:266)\\n\\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\\n\\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\\n\\tat
java.lang.Thread.run(Thread.java:748)\\nCaused by: InvocationException:
code=490;msg=CommonExceptionData [message=Cse Internal Bad Request]\\n\\tat
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.doCreate(ExceptionFactory.java:74)\\n\\tat
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertException(ExceptionFactory.java:119)\\n\\tat
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertConsumerException(ExceptionFactory.java:78)\\n\\tat
org.apache.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:128)\\n\\tat
org.apache.servicecomb.swagger.invocation.Response.createFail(Response.java:121)\\n\\tat
org.apache.servicecomb.swagger.invocation.AsyncResponse.fail(AsyncResponse.java:41)\\n\\tat
org.apache.servicecomb.transport.rest.client.http.VertxHttpMethod.lambda$doMethod$0(VertxHttpMethod.java:67)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleException(HttpClientRequestBase.java:110)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestImpl.handleException(HttpClientRequestImpl.java:50)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.timeout(HttpClientRequestBase.java:155)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.handleTimeout(HttpClientRequestBase.java:140)\\n\\tat
io.vertx.core.http.impl.HttpClientRequestBase.lambda$setTimeout$0(HttpClientRequestBase.java:100)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:782)\\n\\tat
io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:753)\\n\\tat
io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:316)\\n\\tat
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418)\\n\\tat
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)\\n\\tat
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)\\n\\t...
1 more\\nCaused by: java.util.concurrent.TimeoutException: The timeout period
of 30000ms has been exceeded\\n\\t... 11 more\\n\\\"\\n}\"}}"
},
{
"id": 20,
diff --git a/_docs/service-management.md b/_docs/service-management.md
index 5e3e416..3462ce9 100644
--- a/_docs/service-management.md
+++ b/_docs/service-management.md
@@ -20,7 +20,7 @@ Walk through [Develop microservice application in
minutes](/docs/quick-start-bmi
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-bizkeeper</artifactId>
</dependency>
```
diff --git a/_faqs/cn/faq.md b/_faqs/cn/faq.md
index c2d7ac0..c12ee09 100755
--- a/_faqs/cn/faq.md
+++ b/_faqs/cn/faq.md
@@ -32,7 +32,7 @@ redirect_from:
* **Q: 网关依赖的jar和其他微服务的一样吗？**
```xml
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
```
@@ -44,7 +44,7 @@ redirect_from:
* **Q: 服务接口的返回类型可以是任意类型吗？还是必须是responseEntity？**
- A:
可以，具体可以参考java-chassis的[integration-test的实现](https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/integration-tests/springmvc-tests/src/test/java/io/servicecomb/demo/springmvc/tests/SpringMvcIntegrationTestBase.java)。
+ A:
可以，具体可以参考java-chassis的[integration-test的实现](https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/integration-tests/springmvc-tests/src/test/java/org/apache/servicecomb/demo/springmvc/tests/SpringMvcIntegrationTestBase.java)。
* **Q: 微服务启动后，无法正确调用接口，使用的代码为：**
@@ -312,7 +312,7 @@ redirect_from:
3. exclude掉CSE框架引入的log4j，例如：
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>provider-springmvc</artifactId>
<exclusions>
<exclusion>
diff --git a/_faqs/faq.md b/_faqs/faq.md
index c123c7f..a9944bd 100644
--- a/_faqs/faq.md
+++ b/_faqs/faq.md
@@ -21,7 +21,7 @@ last_modified_at: 2017-10-29T10:01:43-04:00
3. **Q: What's the dependency differences between gateway and other
microservices?**
```xml
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
```
@@ -33,7 +33,7 @@ last_modified_at: 2017-10-29T10:01:43-04:00
5. **Q: Are there any restrictions of the return type of our API? Should it be
the type of ResponseEntity?**
- A: No, examples can refer to [the implementation of
integration-test](https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/integration-tests/springmvc-tests/src/test/java/io/servicecomb/demo/springmvc/tests/SpringMvcIntegrationTestBase.java)
in java-chassis.
+ A: No, examples can refer to [the implementation of
integration-test](https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/integration-tests/springmvc-tests/src/test/java/org/apache/servicecomb/demo/springmvc/tests/SpringMvcIntegrationTestBase.java)
in java-chassis.
6. **Q: Our API can not be accessed after microservices are up. It just
returns *404 Not Found*. The codes we use is as follows:**
diff --git a/_posts/2017-06-15-linuxcon-workshop-demo.md
b/_posts/2017-06-15-linuxcon-workshop-demo.md
index 09ff5c1..7eb63ef 100644
--- a/_posts/2017-06-15-linuxcon-workshop-demo.md
+++ b/_posts/2017-06-15-linuxcon-workshop-demo.md
@@ -93,7 +93,7 @@ public interface FibonacciEndpoint {
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
</dependency>
@@ -482,7 +482,7 @@ cse:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-discovery</artifactId>
</dependency>
```
diff --git a/_posts/2017-07-17-tracing-with-servicecomb.md
b/_posts/2017-07-17-tracing-with-servicecomb.md
index c0e0668..f7a5a65 100644
--- a/_posts/2017-07-17-tracing-with-servicecomb.md
+++ b/_posts/2017-07-17-tracing-with-servicecomb.md
@@ -36,7 +36,7 @@ to apply distributed tracing with Zipkin.
A microservice written with ServiceComb Java Chassis just need to add one
dependency below to its pom.xml.
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-tracing-zipkin</artifactId>
</dependency>
@@ -46,7 +46,7 @@ If the microservice is an API gateway with Spring Cloud +
Zuul like manager serv
dependency has to be included.
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul-zipkin</artifactId>
</dependency>
```
diff --git a/_posts/2018-01-10-howto-upgrade-to-zipkin-v2.md
b/_posts/2018-01-10-howto-upgrade-to-zipkin-v2.md
index 5e68e3a..86fbb5f 100644
--- a/_posts/2018-01-10-howto-upgrade-to-zipkin-v2.md
+++ b/_posts/2018-01-10-howto-upgrade-to-zipkin-v2.md
@@ -89,11 +89,11 @@ handlers/handler-tracing-zipkin/pom.xml
Change the zipkin.xxx import to zipkin2.xxx on imports, and most importantly,
use `spanReporter()` instead of `reporter()` for generating reporter for brave,
change the api path to /api/v2/xxx when creating sender.
``` diff
-handlers/handler-tracing-zipkin/src/main/java/io/servicecomb/tracing/zipkin/TracingConfiguration.java
+handlers/handler-tracing-zipkin/src/main/java/org/apache/servicecomb/tracing/zipkin/TracingConfiguration.java
@@ -31,11 +31,11 @@
import brave.http.HttpTracing;
import brave.propagation.CurrentTraceContext;
- import io.servicecomb.config.DynamicProperties;
+ import org.apache.servicecomb.config.DynamicProperties;
-import zipkin.Span;
-import zipkin.reporter.AsyncReporter;
-import zipkin.reporter.Reporter;
@@ -158,11 +158,11 @@ But this will not work. In `zipkin2.Reporter`, the
`create(sender)` is actually
We do not use zipkin.Span in our production code, but we do use it in our
tests. Those changes are quite straight forward, we just change the accessing
of fields to calling methods as described in the What's Changed section.
``` diff
-tracing/tracing-zipkin/src/test/java/io/servicecomb/tracing/zipkin/ZipkinSpanAspectTest.java
+tracing/tracing-zipkin/src/test/java/org/apache/servicecomb/tracing/zipkin/ZipkinSpanAspectTest.java
@@ -45,7 +45,7 @@
- import io.servicecomb.tracing.zipkin.app.ZipkinSpanTestApplication;
- import
io.servicecomb.tracing.zipkin.app.ZipkinSpanTestApplication.CustomSpanTask;
- import
io.servicecomb.tracing.zipkin.app.ZipkinSpanTestApplication.SomeSlowTask;
+ import org.apache.servicecomb.tracing.zipkin.app.ZipkinSpanTestApplication;
+ import
org.apache.servicecomb.tracing.zipkin.app.ZipkinSpanTestApplication.CustomSpanTask;
+ import
org.apache.servicecomb.tracing.zipkin.app.ZipkinSpanTestApplication.SomeSlowTask;
-import zipkin.Span;
+import zipkin2.Span;
diff --git a/_posts/cn/2017-06-15-linuxcon-workshop-demo.md
b/_posts/cn/2017-06-15-linuxcon-workshop-demo.md
index 05e6641..90ac858 100644
--- a/_posts/cn/2017-06-15-linuxcon-workshop-demo.md
+++ b/_posts/cn/2017-06-15-linuxcon-workshop-demo.md
@@ -93,7 +93,7 @@ public interface FibonacciEndpoint {
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
</dependency>
@@ -482,7 +482,7 @@ cse:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-discovery</artifactId>
</dependency>
```
diff --git a/_posts/cn/2017-07-17-tracing-with-servicecomb.md
b/_posts/cn/2017-07-17-tracing-with-servicecomb.md
index a7f1836..d63b55f 100644
--- a/_posts/cn/2017-07-17-tracing-with-servicecomb.md
+++ b/_posts/cn/2017-07-17-tracing-with-servicecomb.md
@@ -31,7 +31,7 @@ ServiceComb 集成了 Zipkin 提供自动调用链追踪能力，如此一来用
基于 ServiceComb Java Chassis 的微服务只需要添加如下依赖到 pom.xml。
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-tracing-zipkin</artifactId>
</dependency>
@@ -40,7 +40,7 @@ ServiceComb 集成了 Zipkin 提供自动调用链追踪能力，如此一来用
如果微服务是基于 Spring Cloud + Zuul 的 API 网关，例如 workshop demo 中的 manager service
，我们还需要加入如下的额外依赖。
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul-zipkin</artifactId>
</dependency>
```
diff --git a/_posts/cn/2017-09-14-maven-dependency-management.md
b/_posts/cn/2017-09-14-maven-dependency-management.md
index 04b5879..23e0b0e 100644
--- a/_posts/cn/2017-09-14-maven-dependency-management.md
+++ b/_posts/cn/2017-09-14-maven-dependency-management.md
@@ -68,9 +68,9 @@ redirect_from:
<dependencyManagement>
<dependencies>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>0.2.0</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -102,9 +102,9 @@ redirect_from:
<scope>import</scope>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>0.2.0</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
diff --git a/_users/application-boot-process.md
b/_users/application-boot-process.md
index 3917ee3..2f7b340 100644
--- a/_users/application-boot-process.md
+++ b/_users/application-boot-process.md
@@ -21,7 +21,7 @@ The starup process of a service provider includes
initializing Log4j, loading be
* Register the microservice.
- After Spring context has been loaded,
`io.servicecomb.core.CseApplicationListener` will configure the handler, load
the information about the provider schema, and the register microservice to
service center.
+ After Spring context has been loaded,
`org.apache.servicecomb.core.CseApplicationListener` will configure the
handler, load the information about the provider schema, and the register
microservice to service center.
> **NOTE:**
> The three level of configuration items for ServiceComb are the configuration
> center, environment variables, and local files, listed in a descending order
> by priority. If configuration items with the same name exist, the one in the
> highest level overwrites others. Configuration items stored in the
> configuration center can be modified during running.
diff --git a/_users/cn/application-boot-process.md
b/_users/cn/application-boot-process.md
index d47b2d4..3f8dbff 100644
--- a/_users/cn/application-boot-process.md
+++ b/_users/cn/application-boot-process.md
@@ -21,7 +21,7 @@ redirect_from:
* 服务注册
- 在Spring
context加载完成后，`io.servicecomb.core.CseApplicationListener`会加载handler配置、加载provider的schema信息，最后将微服务信息注册到服务中心。
+ 在Spring
context加载完成后，`org.apache.servicecomb.core.CseApplicationListener`会加载handler配置、加载provider的schema信息，最后将微服务信息注册到服务中心。
> **说明：**
> ServiceComb的配置项分为三个层次：配置中心、环境变量、本地文件，三者优先级依次递减，高优先级中的配置项覆盖低优先级同名配置项。存放在配置中心的配置项可以在运行时修改。
diff --git a/_users/cn/communicate-protocol.md
b/_users/cn/communicate-protocol.md
index b0be20f..2d813c0 100644
--- a/_users/cn/communicate-protocol.md
+++ b/_users/cn/communicate-protocol.md
@@ -68,11 +68,11 @@ cse:
<param-value>classpath*:META-INF/spring/*.bean.xml
classpath*:app-config.xml</param-value>
</context-param>
<listener>
-
<listener-class>io.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
+
<listener-class>org.apache.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>RestServlet</servlet-name>
-
<servlet-class>io.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
+
<servlet-class>org.apache.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<async-supported>true</async-supported>
</servlet>
@@ -92,7 +92,7 @@ cse:
<param-value>classpath*:META-INF/spring/*.bean.xml
classpath*:app-config.xml</param-value>
</context-param>
<listener>
-
<listener-class>io.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
+
<listener-class>org.apache.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
</listener>
</web-app>
```
@@ -107,7 +107,7 @@ cse:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-rest-servlet</artifactId>
</dependency>
```
@@ -141,8 +141,8 @@ cse:
REST over
Vertx通信通道对应使用standalone部署运行模式，可直接通过main函数拉起。main函数中需要初始化日志和加载服务配置，代码如下：
```java
-import io.servicecomb.foundation.common.utils.BeanUtils;
-import io.servicecomb.foundation.common.utils.Log4jUtils;
+import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
public class MainServer {
public static void main(String[] args) throws Exception {
@@ -156,7 +156,7 @@ public class MainServer {
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-rest-vertx</artifactId>
</dependency>
```
@@ -201,7 +201,7 @@ Highway是ServiceComb的高性能私有协议，用户可在有特殊性能需
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-highway</artifactId>
</dependency>
```
diff --git a/_users/cn/customized-tracing.md b/_users/cn/customized-tracing.md
index 352c6b8..0638774 100644
--- a/_users/cn/customized-tracing.md
+++ b/_users/cn/customized-tracing.md
@@ -35,7 +35,7 @@ redirect_from:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>tracing-zipkin</artifactId>
</dependency>
```
@@ -89,7 +89,7 @@ public class SlowRepoImpl implements SlowRepo {
| key | value |
| :--- | :--- |
| span name | crawl |
-| call.path | public abstract java.lang.String
io.servicecomb.tests.tracing.SlowRepo.crawl\(\) throws
java.lang.InterruptedException |
+| call.path | public abstract java.lang.String
org.apache.servicecomb.tests.tracing.SlowRepo.crawl\(\) throws
java.lang.InterruptedException |
如果需要定制上报的数据内容，可以传入自定义的参数：
diff --git a/_users/cn/define-service-contract.md
b/_users/cn/define-service-contract.md
index 70eb04e..29d1a00 100644
--- a/_users/cn/define-service-contract.md
+++ b/_users/cn/define-service-contract.md
@@ -44,7 +44,7 @@ swagger: '2.0'
info:
title: hello
version: 1.0.0
- x-java-interface: io.servicecomb.samples.common.schema.Hello
+ x-java-interface: org.apache.servicecomb.samples.common.schema.Hello
basePath: /springmvchello
produces:
- application/json
diff --git a/_users/cn/deployment.md b/_users/cn/deployment.md
index 1707d4f..93c37d6 100644
--- a/_users/cn/deployment.md
+++ b/_users/cn/deployment.md
@@ -19,8 +19,8 @@ redirect_from:
* **步骤1** 编写Main函数，初始化日志和加载服务配置，内容如下：
```java
- import io.servicecomb.foundation.common.utils.BeanUtils;
- import io.servicecomb.foundation.common.utils.Log4jUtils;
+ import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+ import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
public class MainServer {
public static void main(String[] args) throws Exception {
Log4jUtils.init(); #日志初始化
@@ -51,12 +51,12 @@ redirect_from:
</param-value>
</context-param>
<listener>
-
<listener-class>io.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
+
<listener-class>org.apache.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>RestServlet</servlet-name>
-
<servlet-class>io.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
+
<servlet-class>org.apache.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<async-supported>true</async-supported>
</servlet>
@@ -72,7 +72,7 @@ redirect_from:
```xml
<dependencies>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-rest-servlet</artifactId>
</dependency>
</dependencies>
diff --git a/_users/cn/develop-with-jax-rs.md b/_users/cn/develop-with-jax-rs.md
index 5a558f7..648713c 100644
--- a/_users/cn/develop-with-jax-rs.md
+++ b/_users/cn/develop-with-jax-rs.md
@@ -40,8 +40,8 @@ ServiceComb支持开发者使用JAX-RS注解，使用JAX-RS模式开发服务。
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import javax.ws.rs.core.MediaType;
- import io.servicecomb.samples.common.schema.Hello;
- import io.servicecomb.samples.common.schema.models.Person;
+ import org.apache.servicecomb.samples.common.schema.Hello;
+ import org.apache.servicecomb.samples.common.schema.models.Person;
@Path("/jaxrshello")
@Produces(MediaType.APPLICATION_JSON)
@@ -67,7 +67,7 @@ ServiceComb支持开发者使用JAX-RS注解，使用JAX-RS模式开发服务。
在服务的实现类上打上注解`@RestSchema`，指定schemaId，表示该实现作为当前微服务的一个schema发布，代码如下：
```java
- import io.servicecomb.provider.rest.common.RestSchema;
+ import org.apache.servicecomb.provider.rest.common.RestSchema;
// other code omitted
@RestSchema(schemaId = "jaxrsHello")
public class JaxrsHelloImpl implements Hello {
@@ -85,7 +85,7 @@ ServiceComb支持开发者使用JAX-RS注解，使用JAX-RS模式开发服务。
xmlns:context=" http://www.springframework.org/schema/context "
xsi:schemaLocation=" http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.huawei.com/schema/paas/cse/rpc
classpath:META-INF/spring/spring-paas-cse-rpc.xsd">
- <context:component-scan
base-package="io.servicecomb.samples.jaxrs.provider"/>
+ <context:component-scan
base-package="org.apache.servicecomb.samples.jaxrs.provider"/>
</beans>
```
diff --git a/_users/cn/develop-with-rest-template.md
b/_users/cn/develop-with-rest-template.md
index 8f1605a..a5b96d5 100644
--- a/_users/cn/develop-with-rest-template.md
+++ b/_users/cn/develop-with-rest-template.md
@@ -26,10 +26,10 @@ redirect_from:
import org.springframework.stereotype.Component;
import org.springframework.web.client.RestTemplate;
-import io.servicecomb.foundation.common.utils.BeanUtils;
-import io.servicecomb.foundation.common.utils.Log4jUtils;
-import io.servicecomb.provider.springmvc.reference.RestTemplateBuilder;
-import io.servicecomb.samples.common.schema.models.Person;
+import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
+import org.apache.servicecomb.provider.springmvc.reference.RestTemplateBuilder;
+import org.apache.servicecomb.samples.common.schema.models.Person;
@Component
public class SpringmvcConsumerMain {
diff --git a/_users/cn/develop-with-rpc.md b/_users/cn/develop-with-rpc.md
index 789b53b..7507cfd 100644
--- a/_users/cn/develop-with-rpc.md
+++ b/_users/cn/develop-with-rpc.md
@@ -21,11 +21,11 @@ RPC开发方式允许用户通过在服务接口上标注注解来生成服务
```java
import org.springframework.stereotype.Component;
-import io.servicecomb.foundation.common.utils.BeanUtils;
-import io.servicecomb.foundation.common.utils.Log4jUtils;
-import io.servicecomb.provider.pojo.RpcReference;
-import io.servicecomb.samples.common.schema.Hello;
-import io.servicecomb.samples.common.schema.models.Person;
+import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
+import org.apache.servicecomb.provider.pojo.RpcReference;
+import org.apache.servicecomb.samples.common.schema.Hello;
+import org.apache.servicecomb.samples.common.schema.models.Person;
@Component
public class CodeFirstConsumerMain {
diff --git a/_users/cn/develop-with-springmvc.md
b/_users/cn/develop-with-springmvc.md
index 572b541..f5d3d5f 100644
--- a/_users/cn/develop-with-springmvc.md
+++ b/_users/cn/develop-with-springmvc.md
@@ -39,8 +39,8 @@ ServiceComb支持SpringMVC注解，允许使用SpringMVC风格开发微服务。
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RequestParam;
- import io.servicecomb.samples.common.schema.Hello;
- import io.servicecomb.samples.common.schema.models.Person;
+ import org.apache.servicecomb.samples.common.schema.Hello;
+ import org.apache.servicecomb.samples.common.schema.models.Person;
@RequestMapping(path = "/springmvchello", produces =
MediaType.APPLICATION_JSON)
public class SpringmvcHelloImpl implements Hello {
@@ -63,7 +63,7 @@ ServiceComb支持SpringMVC注解，允许使用SpringMVC风格开发微服务。
在服务的实现类上打上注解@RestSchema，指定schemaId，表示该实现作为当前微服务的一个schema发布，代码如下：
```java
- import io.servicecomb.provider.rest.common.RestSchema;
+ import org.apache.servicecomb.provider.rest.common.RestSchema;
// other code omitted
@RestSchema(schemaId = "springmvcHello")
public class SpringmvcHelloImpl implements Hello {
@@ -82,7 +82,7 @@ ServiceComb支持SpringMVC注解，允许使用SpringMVC风格开发微服务。
xsi:schemaLocation="http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd";>
- <context:component-scan
base-package="io.servicecomb.samples.springmvc.provider"/>
+ <context:component-scan
base-package="org.apache.servicecomb.samples.springmvc.provider"/>
</beans>
```
diff --git a/_users/cn/develop-with-transparent-rpc.md
b/_users/cn/develop-with-transparent-rpc.md
index ea09019..c4461ea 100644
--- a/_users/cn/develop-with-transparent-rpc.md
+++ b/_users/cn/develop-with-transparent-rpc.md
@@ -37,8 +37,8 @@ redirect_from:
Hello的服务实现如下：
```java
- import io.servicecomb.samples.common.schema.Hello;
- import io.servicecomb.samples.common.schema.models.Person;
+ import org.apache.servicecomb.samples.common.schema.Hello;
+ import org.apache.servicecomb.samples.common.schema.models.Person;
public class HelloImpl implements Hello {
@Override
@@ -65,7 +65,7 @@ redirect_from:
xmlns:context=" http://www.springframework.org/schema/context "
xsi:schemaLocation=" http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.huawei.com/schema/paas/cse/rpc
classpath:META-INF/spring/spring-paas-cse-rpc.xsd">
- <cse:rpc-schema schema-id="pojoHello"
implementation="io.servicecomb.samples.pojo.provider.PojoHelloImpl"/>
+ <cse:rpc-schema schema-id="pojoHello"
implementation="org.apache.servicecomb.samples.pojo.provider.PojoHelloImpl"/>
</beans>
```
@@ -79,7 +79,7 @@ redirect_from:
3. 发布服务。在接口Hello的实现类上使用@RpcSchema注解定义schema，代码如下：
```java
- import io.servicecomb.provider.pojo.RpcSchema;
+ import org.apache.servicecomb.provider.pojo.RpcSchema;
// other code omitted
@RpcSchema(schemaId = "pojoHello")
public class HelloImpl implements Hello {
@@ -97,7 +97,7 @@ redirect_from:
xmlns:context=" http://www.springframework.org/schema/context "
xsi:schemaLocation=" http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.huawei.com/schema/paas/cse/rpc
classpath:META-INF/spring/spring-paas-cse-rpc.xsd">
- <context:component-scan
base-package="io.servicecomb.samples.pojo.provider"/>
+ <context:component-scan
base-package="org.apache.servicecomb.samples.pojo.provider"/>
</beans>
```
diff --git a/_users/cn/distributed-tracing.md b/_users/cn/distributed-tracing.md
index 4d97416..8a4160a 100644
--- a/_users/cn/distributed-tracing.md
+++ b/_users/cn/distributed-tracing.md
@@ -34,7 +34,7 @@ ServiceComb 集成了 Zipkin 提供自动调用链追踪能力，如此一来用
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-tracing-zipkin</artifactId>
</dependency>
```
@@ -43,7 +43,7 @@ ServiceComb 集成了 Zipkin 提供自动调用链追踪能力，如此一来用
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul-zipkin</artifactId>
</dependency>
```
diff --git a/_users/cn/metrics-in-1.0.0-m1.md b/_users/cn/metrics-in-1.0.0-m1.md
index d8e4614..9c93f3e 100644
--- a/_users/cn/metrics-in-1.0.0-m1.md
+++ b/_users/cn/metrics-in-1.0.0-m1.md
@@ -137,7 +137,7 @@ servicecomb:
只需要添加metrics-core依赖即可：
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>metrics-core</artifactId>
<version>1.0.0-m1</version>
</dependency>
@@ -194,7 +194,7 @@ cse:
```
你就可以通过http://localhost:8080/metrics 直接获取到数据，打开浏览器输入此URL就可以看到返回结果。
### 直接代码获取
-从上面的代码可以看到，数据提供Bean接口是io.servicecomb.metrics.core.publish.DataSource，因此如果你希望自己开发数据发布程序，只需要注入它即可。
+从上面的代码可以看到，数据提供Bean接口是org.apache.servicecomb.metrics.core.publish.DataSource，因此如果你希望自己开发数据发布程序，只需要注入它即可。
```java
@Autowired
private DataSource dataSource;
diff --git a/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
b/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
index 58809b2..559ad62 100644
--- a/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
+++ b/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
@@ -30,7 +30,7 @@ Prometheus推荐Pull模式拉取Metrics数据，被监控微服务作为Producer
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>metrics-core</artifactId>
</dependency>
```
@@ -45,7 +45,7 @@ cse:
rest:
address: 0.0.0.0:8080
```
-你就可以通过http://localhost:8080/metrics
直接获取到Metrics数据，它返回的是io.servicecomb.metrics.common.RegistryMetric实体对象，输出格式为：
+你就可以通过http://localhost:8080/metrics
直接获取到Metrics数据，它返回的是org.apache.servicecomb.metrics.common.RegistryMetric实体对象，输出格式为：
```json
{"instanceMetric":{
"systemMetric":{"cpuLoad":10.0,"cpuRunningThreads":39,"heapInit":266338304,"heapMax":3786407936,"heapCommit":626524160,"heapUsed":338280024,"nonHeapInit":2555904,"nonHeapMax":-1,"nonHeapCommit":60342272,"nonHeapUsed":58673152},
@@ -102,7 +102,7 @@ servicecomb:
只需要添加metrics-prometheus依赖即可：
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>metrics-prometheus</artifactId>
<version>1.0.0-m1</version>
</dependency>
diff --git a/_users/cn/metrics-write-file-extension-and-sample-in-1.0.0-m1.md
b/_users/cn/metrics-write-file-extension-and-sample-in-1.0.0-m1.md
index 8bb548f..81de0f1 100644
--- a/_users/cn/metrics-write-file-extension-and-sample-in-1.0.0-m1.md
+++ b/_users/cn/metrics-write-file-extension-and-sample-in-1.0.0-m1.md
@@ -58,7 +58,7 @@ servicecomb:
1. 首先需要引入metrics-write-file模块，这个模块包含了获取Metrics数据并转化为指定格式后写文件的逻辑：
```xml
<dependency>
- <groupId>io.servicecomb.samples</groupId>
+ <groupId>org.apache.servicecomb.samples</groupId>
<artifactId>metrics-write-file</artifactId>
</dependency>
```
@@ -83,7 +83,7 @@ Java Chassis集成了Spring Boot Starter，如果使用Spring Boot Starter启动
<!--servicecomb spring boot starter-->
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
</dependency>
```
diff --git a/_users/cn/service-configurations.md
b/_users/cn/service-configurations.md
index 66e64bb..5ceceb6 100644
--- a/_users/cn/service-configurations.md
+++ b/_users/cn/service-configurations.md
@@ -23,7 +23,7 @@ redirect_from:
| 配置项 | 默认值 | 取值范围 | 是否必选 | 含义 | 注意 |
| :--- | :--- | :--- | :--- | :--- | :--- |
-| cse.loadbalance.NFLoadBalancerRuleClassName |
com.netflix.loadbalancer.RoundRobinRule |
com.netflix.loadbalancer.RoundRobinRule（轮询）com.netflix.loadbalancer.RandomRule（随机）com.netflix.loadbalancer.WeightedResponseTimeRule（服务器响应时间权值）io.servicecomb.loadbalance.SessionStickinessRule（会话保持）
| 否 | 负载均衡路由策略 | - |
+| cse.loadbalance.NFLoadBalancerRuleClassName |
com.netflix.loadbalancer.RoundRobinRule |
com.netflix.loadbalancer.RoundRobinRule（轮询）com.netflix.loadbalancer.RandomRule（随机）com.netflix.loadbalancer.WeightedResponseTimeRule（服务器响应时间权值）org.apache.servicecomb.loadbalance.SessionStickinessRule（会话保持）
| 否 | 负载均衡路由策略 | - |
| cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds | 30 | Integer
| 否 | 客户端闲置时间，超过限制后选择后面的服务器。 | 暂不支持微服务配置。e.g.
cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds，不能配置为cse.loadbalance.DemoService.SessionStickinessRule.sessionTimeoutInSeconds
|
| cse.loadbalance.SessionStickinessRule.successiveFailedTimes | 5 | Integer |
否 | 客户端失败次数，超过后会切换服务器 | 暂不支持微服务配置 |
| cse.loadbalance.retryEnabled | FALSE | Boolean | 否 | 负载均衡捕获到服务调用异常，是否进行重试 |
- |
@@ -33,7 +33,7 @@ redirect_from:
| cse.loadbalance.isolation.enableRequestThreshold | 20 | Integer | 否 |
当实例的调用总次数达到该值时开始进入隔离逻辑门槛 | - |
| cse.loadbalance.isolation.errorThresholdPercentage | 20 |
Integer，区间为\(0,100\] | 否 | 实例故障隔离错误百分比 | - |
| cse.loadbalance.isolation.singleTestTime | 10000 | Integer | 否 | 故障实例单点测试时间
| 单位为ms |
-| cse.loadbalance.transactionControl.policy |
io.servicecomb.loadbalance.filter.SimpleTransactionControlFilter | - | 否 |
动态路由分流策略 | 框架提供了简单的分流机制，开发者也可以实现自定义的分流过滤策略 |
+| cse.loadbalance.transactionControl.policy |
org.apache.servicecomb.loadbalance.filter.SimpleTransactionControlFilter | - |
否 | 动态路由分流策略 | 框架提供了简单的分流机制，开发者也可以实现自定义的分流过滤策略 |
| cse.loadbalance.transactionControl.options | - | key/value pairs | 否 |
针对SimpleTransactionControlFilter分流策略的配置项，可添加任意项过滤标签 | - |
### 示例代码
@@ -67,11 +67,11 @@ cse：
用户可以在ServiceComb提供的路由策略框架下根据业务需要，通过编程的方式来开发路由策略。实施步骤如下：
* 实现接口`com.netflix.loadbalancer.IRule`中定义的接口方法。
-路由选择逻辑在public Server choose\(Object
key\)方法中实现。LoadBalancerStats是一个封装了负载均衡器当前运行状态的一个结构。通过获取stats中各个实例的运行指标，在choose方法中，判定将当前请求路由到哪个实例上进行处理。处理风格可以参照`io.servicecomb.loadbalance.SessionStickinessRule`。
+路由选择逻辑在public Server choose\(Object
key\)方法中实现。LoadBalancerStats是一个封装了负载均衡器当前运行状态的一个结构。通过获取stats中各个实例的运行指标，在choose方法中，判定将当前请求路由到哪个实例上进行处理。处理风格可以参照`org.apache.servicecomb.loadbalance.SessionStickinessRule`。
* 编译开发的策略，保证生成的class在classpath下。
-* 通过SDK配置该路由策略，假如是`AbcRule`。则配置如下：
`cse.loadbalance.NFLoadBalancerRuleClassName=io.servicecomb.ribbon.rule.AbcRule`
+* 通过SDK配置该路由策略，假如是`AbcRule`。则配置如下：
`cse.loadbalance.NFLoadBalancerRuleClassName=org.apache.servicecomb.ribbon.rule.AbcRule`
## 限流策略
### 场景描述
diff --git a/_users/cn/service-definition.md b/_users/cn/service-definition.md
index 8397f00..364e21c 100644
--- a/_users/cn/service-definition.md
+++ b/_users/cn/service-definition.md
@@ -47,9 +47,9 @@ service_description: #服务描述
allowCrossApp: false
key1: value1
key2: value2
- propertyExtentedClass:
io.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
+ propertyExtentedClass:
org.apache.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
instance_description: #实例描述
properties: #元数据
key3: value3
- propertyExtentedClass:
io.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
+ propertyExtentedClass:
org.apache.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
```
diff --git a/_users/cn/service-heartbeat.md b/_users/cn/service-heartbeat.md
index dc808ae..6bfae99 100644
--- a/_users/cn/service-heartbeat.md
+++ b/_users/cn/service-heartbeat.md
@@ -16,7 +16,7 @@ redirect_from:
## 涉及API
-* `io.servicecomb.serviceregistry.client.ServiceRegistryClient`：服务中心客户端
+* `org.apache.servicecomb.serviceregistry.client.ServiceRegistryClient`：服务中心客户端
## 配置说明
diff --git a/_users/cn/use-servicecomb-in-spring-boot.md
b/_users/cn/use-servicecomb-in-spring-boot.md
index bea1a0c..7ff58c5 100644
--- a/_users/cn/use-servicecomb-in-spring-boot.md
+++ b/_users/cn/use-servicecomb-in-spring-boot.md
@@ -45,7 +45,7 @@ redirect_from:
<dependency>
<groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>1.0.0-m1-SNAPSHOT</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -173,7 +173,7 @@ redirect_from:
<dependency>
<groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>1.0.0-m1-SNAPSHOT</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
diff --git a/_users/cn/use-tls.md b/_users/cn/use-tls.md
index f7d9b04..1df8fab 100644
--- a/_users/cn/use-tls.md
+++ b/_users/cn/use-tls.md
@@ -63,7 +63,7 @@ ssl.[tag].[property]
| ssl.keyStoreType | PKCS12 | - | 否 | 身份证书类型 | - |
| ssl.keyStoreValue | - | - | 否 | 身份证书密码 | - |
| ssl.crl | revoke.crl | - | 否 | 吊销证书文件 | - |
-| ssl.sslCustomClass | - | io.servicecomb.foundation.ssl.SSLCustom的实现类 | 否 |
SSLCustom类的实现，用于开发者转换密码、文件路径等。 | - |
+| ssl.sslCustomClass | - | org.apache.servicecomb.foundation.ssl.SSLCustom的实现类
| 否 | SSLCustom类的实现，用于开发者转换密码、文件路径等。 | - |
> **说明**：
>
@@ -138,5 +138,5 @@ ssl.keyStore: server.p12
ssl.keyStoreType: PKCS12
ssl.keyStoreValue: Changeme_123
ssl.crl: revoke.crl
-ssl.sslCustomClass: io.servicecomb.demo.DemoSSLCustom
+ssl.sslCustomClass: org.apache.servicecomb.demo.DemoSSLCustom
```
diff --git a/_users/cn/zuul.md b/_users/cn/zuul.md
index fd46e62..140097a 100644
--- a/_users/cn/zuul.md
+++ b/_users/cn/zuul.md
@@ -60,7 +60,7 @@ Zuul做API Gateway，即建立一个Zuul Proxy应用，在该Proxy应用中统
<artifactId>spring-cloud-starter-hystrix</artifactId>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-discovery</artifactId>
</dependency>
```
diff --git a/_users/communicate-protocol.md b/_users/communicate-protocol.md
index 30d3934..23f394a 100644
--- a/_users/communicate-protocol.md
+++ b/_users/communicate-protocol.md
@@ -68,11 +68,11 @@ cse:
<param-value>classpath*:META-INF/spring/*.bean.xml
classpath*:app-config.xml</param-value>
</context-param>
<listener>
-
<listener-class>io.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
+
<listener-class>org.apache.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>RestServlet</servlet-name>
-
<servlet-class>io.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
+
<servlet-class>org.apache.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<async-supported>true</async-supported>
</servlet>
@@ -92,7 +92,7 @@ cse:
<param-value>classpath*:META-INF/spring/*.bean.xml
classpath*:app-config.xml</param-value>
</context-param>
<listener>
-
<listener-class>io.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
+
<listener-class>org.apache.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
</listener>
</web-app>
```
@@ -107,7 +107,7 @@ The two method are equivalent, and they both require that
the following dependen
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-rest-servlet</artifactId>
</dependency>
```
@@ -141,8 +141,8 @@ cse:
The REST over Vertx communication channel uses the standalone running mode
that can be started using the main function. In the main function, you need to
initialize logs and load service configuration. The code is as follow:
```java
-import io.servicecomb.foundation.common.utils.BeanUtils;
-import io.servicecomb.foundation.common.utils.Log4jUtils;
+import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
public class MainServer {
public static void main(String[] args) throws Exception {
@@ -156,7 +156,7 @@ To use the REST over Vertx communication channel, you need
to add the following
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-rest-vertx</artifactId>
</dependency>
```
@@ -201,7 +201,7 @@ To use the Highway communication channel, you need to add
the following dependen
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-highway</artifactId>
</dependency>
```
diff --git a/_users/customized-tracing.md b/_users/customized-tracing.md
index ef08da5..9e58a1c 100644
--- a/_users/customized-tracing.md
+++ b/_users/customized-tracing.md
@@ -35,7 +35,7 @@ For microservices based on ServiceComb Java Chassis, add the
following content t
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>tracing-zipkin</artifactId>
</dependency>
```
@@ -89,7 +89,7 @@ The call chain reported by customized dotting contains the
following pieces of d
| key | value |
| :-------- | :--------------------------------------- |
| span name | crawl |
-| call.path | public abstract java.lang.String
io.servicecomb.tests.tracing.SlowRepo.crawl\(\) throws
java.lang.InterruptedException |
+| call.path | public abstract java.lang.String
org.apache.servicecomb.tests.tracing.SlowRepo.crawl\(\) throws
java.lang.InterruptedException |
To customize reported data, you can specify customized parameters:
diff --git a/_users/define-service-contract.md
b/_users/define-service-contract.md
index afd5f79..a98f232 100644
--- a/_users/define-service-contract.md
+++ b/_users/define-service-contract.md
@@ -44,7 +44,7 @@ swagger: '2.0'
info:
title: hello
version: 1.0.0
- x-java-interface: io.servicecomb.samples.common.schema.Hello
+ x-java-interface: org.apache.servicecomb.samples.common.schema.Hello
basePath: /springmvchello
produces:
- application/json
diff --git a/_users/deployment.md b/_users/deployment.md
index c953589..7df8a26 100644
--- a/_users/deployment.md
+++ b/_users/deployment.md
@@ -23,8 +23,8 @@ The service container is only a simple Main method, and a
simple Spring containe
* **Step 1** Compile the Main function to initialize logs and load service
configurations. The contents are as follows:
```java
- import io.servicecomb.foundation.common.utils.BeanUtils;
- import io.servicecomb.foundation.common.utils.Log4jUtils;
+ import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+ import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
public class MainServer {
public static void main(String[] args) throws Exception {
Log4jUtils.init(); #Log initialization
@@ -55,12 +55,12 @@ If you need to load the microservice to the web container,
create a sersvlet pro
</param-value>
</context-param>
<listener>
-
<listener-class>io.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
+
<listener-class>org.apache.servicecomb.transport.rest.servlet.RestServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>RestServlet</servlet-name>
-
<servlet-class>io.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
+
<servlet-class>org.apache.servicecomb.transport.rest.servlet.RestServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<async-supported>true</async-supported>
</servlet>
@@ -76,7 +76,7 @@ If you need to load the microservice to the web container,
create a sersvlet pro
```xml
<dependencies>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>transport-rest-servlet</artifactId>
</dependency>
</dependencies>
diff --git a/_users/develop-with-jax-rs.md b/_users/develop-with-jax-rs.md
index 0e16f84..38d16cf 100644
--- a/_users/develop-with-jax-rs.md
+++ b/_users/develop-with-jax-rs.md
@@ -36,8 +36,8 @@ ServiceComb supports developers in developing services in
JAX-RS mode by using J
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import javax.ws.rs.core.MediaType;
- import io.servicecomb.samples.common.schema.Hello;
- import io.servicecomb.samples.common.schema.models.Person;
+ import org.apache.servicecomb.samples.common.schema.Hello;
+ import org.apache.servicecomb.samples.common.schema.models.Person;
@Path("/jaxrshello")
@Produces(MediaType.APPLICATION_JSON)
@@ -61,7 +61,7 @@ ServiceComb supports developers in developing services in
JAX-RS mode by using J
* **Step 3** Release the service. Add ```@RestSchema``` as the annotation of
the service implementation class and specify schemaID, which indicates that the
implementation is released as a schema of the current microservice. The code is
as follows:
```java
- import io.servicecomb.provider.rest.common.RestSchema;
+ import org.apache.servicecomb.provider.rest.common.RestSchema;
// other code omitted
@RestSchema(schemaId = "jaxrsHello")
public class JaxrsHelloImpl implements Hello {
@@ -79,7 +79,7 @@ ServiceComb supports developers in developing services in
JAX-RS mode by using J
xmlns:context=" http://www.springframework.org/schema/context "
xsi:schemaLocation=" http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.huawei.com/schema/paas/cse/rpc
classpath:META-INF/spring/spring-paas-cse-rpc.xsd">
- <context:component-scan
base-package="io.servicecomb.samples.jaxrs.provider"/>
+ <context:component-scan
base-package="org.apache.servicecomb.samples.jaxrs.provider"/>
</beans>
```
diff --git a/_users/develop-with-rest-template.md
b/_users/develop-with-rest-template.md
index 59757d4..3c1ea65 100644
--- a/_users/develop-with-rest-template.md
+++ b/_users/develop-with-rest-template.md
@@ -26,10 +26,10 @@ redirect_from:
import org.springframework.stereotype.Component;
import org.springframework.web.client.RestTemplate;
-import io.servicecomb.foundation.common.utils.BeanUtils;
-import io.servicecomb.foundation.common.utils.Log4jUtils;
-import io.servicecomb.provider.springmvc.reference.RestTemplateBuilder;
-import io.servicecomb.samples.common.schema.models.Person;
+import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
+import org.apache.servicecomb.provider.springmvc.reference.RestTemplateBuilder;
+import org.apache.servicecomb.samples.common.schema.models.Person;
@Component
public class SpringmvcConsumerMain {
diff --git a/_users/develop-with-rpc.md b/_users/develop-with-rpc.md
index da439fd..032e31d 100644
--- a/_users/develop-with-rpc.md
+++ b/_users/develop-with-rpc.md
@@ -21,11 +21,11 @@ To call a microservice, you only need to declare a member
of a service API type
```java
import org.springframework.stereotype.Component;
-import io.servicecomb.foundation.common.utils.BeanUtils;
-import io.servicecomb.foundation.common.utils.Log4jUtils;
-import io.servicecomb.provider.pojo.RpcReference;
-import io.servicecomb.samples.common.schema.Hello;
-import io.servicecomb.samples.common.schema.models.Person;
+import org.apache.servicecomb.foundation.common.utils.BeanUtils;
+import org.apache.servicecomb.foundation.common.utils.Log4jUtils;
+import org.apache.servicecomb.provider.pojo.RpcReference;
+import org.apache.servicecomb.samples.common.schema.Hello;
+import org.apache.servicecomb.samples.common.schema.models.Person;
@Component
public class CodeFirstConsumerMain {
diff --git a/_users/develop-with-springmvc.md b/_users/develop-with-springmvc.md
index 25cb280..92cc901 100644
--- a/_users/develop-with-springmvc.md
+++ b/_users/develop-with-springmvc.md
@@ -35,8 +35,8 @@ ServiceComb supports Spring MVC remark and allows you to
develop microservices i
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RequestParam;
- import io.servicecomb.samples.common.schema.Hello;
- import io.servicecomb.samples.common.schema.models.Person;
+ import org.apache.servicecomb.samples.common.schema.Hello;
+ import org.apache.servicecomb.samples.common.schema.models.Person;
@RequestMapping(path = "/springmvchello", produces =
MediaType.APPLICATION_JSON)
public class SpringmvcHelloImpl implements Hello {
@@ -57,7 +57,7 @@ ServiceComb supports Spring MVC remark and allows you to
develop microservices i
* **Step 3** Release the service. Add @RestSchema as the annotation of the
service implementation class and specify schemaId, which indicates that the
implementation is released as a schema of the current microservice. The code is
as follows:
```java
- import io.servicecomb.provider.rest.common.RestSchema;
+ import org.apache.servicecomb.provider.rest.common.RestSchema;
// other code omitted
@RestSchema(schemaId = "springmvcHello")
public class SpringmvcHelloImpl implements Hello {
@@ -76,7 +76,7 @@ ServiceComb supports Spring MVC remark and allows you to
develop microservices i
xsi:schemaLocation="http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd";>
- <context:component-scan
base-package="io.servicecomb.samples.springmvc.provider"/>
+ <context:component-scan
base-package="org.apache.servicecomb.samples.springmvc.provider"/>
</beans>
```
diff --git a/_users/develop-with-transparent-rpc.md
b/_users/develop-with-transparent-rpc.md
index 4525dc8..8519b01 100644
--- a/_users/develop-with-transparent-rpc.md
+++ b/_users/develop-with-transparent-rpc.md
@@ -33,8 +33,8 @@ The transparent RPC development mode supports two service
release mode: Spring X
* **Step 2** implement the service. The implementation of the Hello service is
as follows:
```java
- import io.servicecomb.samples.common.schema.Hello;
- import io.servicecomb.samples.common.schema.models.Person;
+ import org.apache.servicecomb.samples.common.schema.Hello;
+ import org.apache.servicecomb.samples.common.schema.models.Person;
public class HelloImpl implements Hello {
@Override
@@ -59,7 +59,7 @@ The transparent RPC development mode supports two service
release mode: Spring X
xmlns:context=" http://www.springframework.org/schema/context "
xsi:schemaLocation=" http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.huawei.com/schema/paas/cse/rpc
classpath:META-INF/spring/spring-paas-cse-rpc.xsd">
- <cse:rpc-schema schema-id="pojoHello"
implementation="io.servicecomb.samples.pojo.provider.PojoHelloImpl"/>
+ <cse:rpc-schema schema-id="pojoHello"
implementation="org.apache.servicecomb.samples.pojo.provider.PojoHelloImpl"/>
</beans>
```
@@ -75,7 +75,7 @@ The transparent RPC development mode supports two service
release mode: Spring X
3. Release the service. @RpcSchema is used to define schema during the API
Hello implementation. The code is as followss:
```java
- import io.servicecomb.provider.pojo.RpcSchema;
+ import org.apache.servicecomb.provider.pojo.RpcSchema;
// other code omitted
@RpcSchema(schemaId = "pojoHello")
public class HelloImpl implements Hello {
@@ -93,7 +93,7 @@ The transparent RPC development mode supports two service
release mode: Spring X
xmlns:context=" http://www.springframework.org/schema/context "
xsi:schemaLocation=" http://www.springframework.org/schema/beans
classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.huawei.com/schema/paas/cse/rpc
classpath:META-INF/spring/spring-paas-cse-rpc.xsd">
- <context:component-scan
base-package="io.servicecomb.samples.pojo.provider"/>
+ <context:component-scan
base-package="org.apache.servicecomb.samples.pojo.provider"/>
</beans>
```
diff --git a/_users/distributed-tracing.md b/_users/distributed-tracing.md
index 253064f..7ce39f6 100644
--- a/_users/distributed-tracing.md
+++ b/_users/distributed-tracing.md
@@ -34,7 +34,7 @@ For microservice based on ServiceComb Java Chassis, add the
following content to
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>handler-tracing-zipkin</artifactId>
</dependency>
```
@@ -43,7 +43,7 @@ If the microservice is based on the API of Spring Cloud Zuul,
such as the manage
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-cloud-zuul-zipkin</artifactId>
</dependency>
```
diff --git a/_users/faq.md b/_users/faq.md
index 221c851..8e37f41 100644
--- a/_users/faq.md
+++ b/_users/faq.md
@@ -23,7 +23,7 @@ redirect_from:
3. **Q: What's the dependency differences between gateway and other
microservices?**
```xml
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-provider</artifactId>
```
@@ -35,7 +35,7 @@ redirect_from:
5. **Q: Are there any restrictions of the return type of our API? Should it be
the type of ResponseEntity?**
- A: No, examples can refer to [the implementation of
integration-test](https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/integration-tests/springmvc-tests/src/test/java/io/servicecomb/demo/springmvc/tests/SpringMvcIntegrationTestBase.java)
in java-chassis.
+ A: No, examples can refer to [the implementation of
integration-test](https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/integration-tests/springmvc-tests/src/test/java/org/apache/servicecomb/demo/springmvc/tests/SpringMvcIntegrationTestBase.java)
in java-chassis.
6. **Q: Our API can not be accessed after microservices are up. It just
returns *404 Not Found*. The codes we use is as follows:**
diff --git a/_users/metrics-in-1.0.0-m1.md b/_users/metrics-in-1.0.0-m1.md
index 79cfb2e..38f042a 100644
--- a/_users/metrics-in-1.0.0-m1.md
+++ b/_users/metrics-in-1.0.0-m1.md
@@ -139,7 +139,7 @@ servicecomb:
We just only need add metrics-core dependency:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>metrics-core</artifactId>
<version>1.0.0-m1</version>
</dependency>
@@ -196,7 +196,7 @@ cse:
```
You can open a browser and input http://localhost:8080/metrics direct get
metrics data.
### Direct programming get
-From above code you can known,the interface of data provider bean is
io.servicecomb.metrics.core.publish.DataSource,so if you want develop your own
metrics publisher,autowired it is enough.
+From above code you can known,the interface of data provider bean is
org.apache.servicecomb.metrics.core.publish.DataSource,so if you want develop
your own metrics publisher,autowired it is enough.
```java
@Autowired
private DataSource dataSource;
diff --git a/_users/metrics-integration-with-prometheus-in-1.0.0-m1.md
b/_users/metrics-integration-with-prometheus-in-1.0.0-m1.md
index 10da41d..657789a 100644
--- a/_users/metrics-integration-with-prometheus-in-1.0.0-m1.md
+++ b/_users/metrics-integration-with-prometheus-in-1.0.0-m1.md
@@ -30,7 +30,7 @@ As an integration(optional) module,the implementation code is
in metrics-integra
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>metrics-core</artifactId>
</dependency>
```
@@ -45,7 +45,7 @@ cse:
rest:
address: 0.0.0.0:8080
```
-You can direct get metrics data at http://localhost:8080/metrics ,it will
return a entity of io.servicecomb.metrics.common.RegistryMetric,the output is:
+You can direct get metrics data at http://localhost:8080/metrics ,it will
return a entity of org.apache.servicecomb.metrics.common.RegistryMetric,the
output is:
```json
{"instanceMetric":{
"systemMetric":{"cpuLoad":10.0,"cpuRunningThreads":39,"heapInit":266338304,"heapMax":3786407936,"heapCommit":626524160,"heapUsed":338280024,"nonHeapInit":2555904,"nonHeapMax":-1,"nonHeapCommit":60342272,"nonHeapUsed":58673152},
@@ -101,7 +101,7 @@ servicecomb:
We just only need add metrics-prometheus dependency:
```xml
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>metrics-prometheus</artifactId>
<version>1.0.0-m1</version>
</dependency>
diff --git a/_users/service-configurations.md b/_users/service-configurations.md
index 2ac3c56..9aa9a97 100644
--- a/_users/service-configurations.md
+++ b/_users/service-configurations.md
@@ -23,7 +23,7 @@ redirect_from:
| Configuration Items | Default Value
| Value Range | Mandatory | Description
| Remarks |
| :--------------------------------------- |
:--------------------------------------- |
:--------------------------------------- | :-------- |
:--------------------------------------- |
:--------------------------------------- |
-| cse.loadbalance.NFLoadBalancerRuleClassName |
com.netflix.loadbalancer.RoundRobinRule |
com.netflix.loadbalancer.RoundRobinRule（polling）com.netflix.loadbalancer.RandomRule（random）com.netflix.loadbalancer.WeightedResponseTimeRule（server
response time weight）io.servicecomb.loadbalance.SessionStickinessRule（session
stickiness） | No | Specifiles the load balancing policy | -
|
+| cse.loadbalance.NFLoadBalancerRuleClassName |
com.netflix.loadbalancer.RoundRobinRule |
com.netflix.loadbalancer.RoundRobinRule（polling）com.netflix.loadbalancer.RandomRule（random）com.netflix.loadbalancer.WeightedResponseTimeRule（server
response time
weight）org.apache.servicecomb.loadbalance.SessionStickinessRule（session
stickiness） | No | Specifiles the load balancing policy | -
|
| cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds | 30
| Integer | No
| Specifies the idle time of a client. If the idle time exceeds the set
value, ServiceComb will select another server. | Currently, this parameter
cannot be set for a certain microservice. For example,
cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds cannot be set to
cse.loadbalance.DemoService.SessionStickinessRule.sessionTimeoutInSeconds |
| cse.loadbalance.SessionStickinessRule.successiveFailedTimes | 5
| Integer | No
| Specifies the number of failed requests from the client. If the number
exceeds the set value, ServiceComb will switch to another server | Currently,
this parameter cannot be set for a certain microservice. |
| cse.loadbalance.retryEnabled | FALSE
| Boolean | No | Specifies
whether to call a service again when a exception is captured by the load
balance. | - |
@@ -33,7 +33,7 @@ redirect_from:
| cse.loadbalance.isolation.enableRequestThreshold | 20
| Integer | No |
Specifies the threshold number of instance calls. If this value is reached,
isolation is enabled. | - |
| cse.loadbalance.isolation.errorThresholdPercentage | 20
| Integer，\(0,100\] | No |
Specifies the error percentage. Instance fault isolation is enabled when the
set value is reached. | - |
| cse.loadbalance.isolation.singleTestTime | 10000
| Integer | No | Specifies the
duration of a faulty instance test on a single node. | This unit is ms.
|
-| cse.loadbalance.transactionControl.policy |
io.servicecomb.loadbalance.filter.SimpleTransactionControlFilter | -
| No | Specifies the offload policies for
dynamic routing. | The framework provides simple offload mechanisms. You can
also customize offload policies. |
+| cse.loadbalance.transactionControl.policy |
org.apache.servicecomb.loadbalance.filter.SimpleTransactionControlFilter | -
| No | Specifies the offload
policies for dynamic routing. | The framework provides simple offload
mechanisms. You can also customize offload policies. |
| cse.loadbalance.transactionControl.options | -
| key/value pairs | No | Specifies the
parameter configured for the SimpleTransactionControlFilter offload policy. You
can add any filtration tag for this item. | -
|
### Sample Code
@@ -66,11 +66,11 @@ cse：
Based on the routing policy framework provided by ServiceComb, you can
program to customize routing policies as required. Perform the following steps:
-* Encode using the API method defined in the `com.netflix.loadbalancer.IRule`
API. Encode in the public Server choose(Object key) method. LoadBalancerStats
is a structure that encapsulates the running state of the load balancer.
Determine on which instance the current routing request will be processed based
on the running indexes of each instance by using the Server choose(Object key)
method. Use method `io.servicecomb.loadbalance.SessionStickinessRule`for
instance processing.
+* Encode using the API method defined in the `com.netflix.loadbalancer.IRule`
API. Encode in the public Server choose(Object key) method. LoadBalancerStats
is a structure that encapsulates the running state of the load balancer.
Determine on which instance the current routing request will be processed based
on the running indexes of each instance by using the Server choose(Object key)
method. Use method
`org.apache.servicecomb.loadbalance.SessionStickinessRule`for instance
processing.
* Compile the developed policy and ensure that the generated class is under
classpath.
-* Use the software development kit(SDK) to configure the routing policy. Use
AbcRule as a routing policy example. The configuration is as follows:
`cse.loadbalance.NFLoadBalancerRuleClassName=io.servicecomb.ribbon.rule.AbcRule`
+* Use the software development kit(SDK) to configure the routing policy. Use
AbcRule as a routing policy example. The configuration is as follows:
`cse.loadbalance.NFLoadBalancerRuleClassName=org.apache.servicecomb.ribbon.rule.AbcRule`
## Rate Limiting Policy
### Scenario
diff --git a/_users/service-definition.md b/_users/service-definition.md
index 6f8914d..56576d0 100644
--- a/_users/service-definition.md
+++ b/_users/service-definition.md
@@ -47,9 +47,9 @@ service_description: #Service description
allowCrossApp: false
key1: value1
key2: value2
- propertyExtentedClass:
io.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
+ propertyExtentedClass:
org.apache.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
instance_description: #Instance description
properties: #Metadata
key3: value3
- propertyExtentedClass:
io.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
+ propertyExtentedClass:
org.apache.servicecomb.serviceregistry.MicroServicePropertyExtendedStub
```
diff --git a/_users/service-heartbeat.md b/_users/service-heartbeat.md
index 2a776a1..7b9ef6a 100644
--- a/_users/service-heartbeat.md
+++ b/_users/service-heartbeat.md
@@ -16,7 +16,7 @@ After a microservice instance is registered in the service
center, the microserv
## Involved APIs
-* `io.servicecomb.serviceregistry.client.ServiceRegistryClient` is the service
client.
+* `org.apache.servicecomb.serviceregistry.client.ServiceRegistryClient` is the
service client.
`ServiceRegistryClient` provides heartbeat to send heartbeats. You can call it
as required. The sample code is as follows:
diff --git a/_users/use-servicecomb-in-spring-boot.md
b/_users/use-servicecomb-in-spring-boot.md
index a7e22b3..44f1ae3 100644
--- a/_users/use-servicecomb-in-spring-boot.md
+++ b/_users/use-servicecomb-in-spring-boot.md
@@ -45,7 +45,7 @@ NOTE， If your java chassis version is or below 0.5.0, please
use the io.servic
<dependency>
<groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>1.0.0-SNAPSHOT</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -171,7 +171,7 @@ This section describes advantages and procedures of
integrating the Spring Boot
<dependency>
<groupId>org.apache.servicecomb</groupId>
<artifactId>java-chassis-dependencies</artifactId>
- <version>1.0.0-SNAPSHOT</version>
+ <version>1.0.0-m1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -186,7 +186,7 @@ This section describes advantages and procedures of
integrating the Spring Boot
```xml
<dependency>
<groupId>org.apache.servicecomb</groupId>
- <artifactId>spring-boot-starter-provider</artifactId>
+ <artifactId>spring-boot-starter-provider</artifactId>
</dependency>
```
diff --git a/_users/use-tls.md b/_users/use-tls.md
index a64612e..b92cce3 100644
--- a/_users/use-tls.md
+++ b/_users/use-tls.md
@@ -63,7 +63,7 @@ For details about the certificate configuration items, see
Table 1.
| ssl.keyStoreType | PKCS12 | -
| No | Specifies the type of identity
certificate. | - |
| ssl.keyStoreValue | - | -
| No | Specifies the password of identity
certificate. | - |
| ssl.crl | revoke.crl | -
| No | Specifies the certificate revocation
list(CRL) file. | - |
-| ssl.sslCustomClass | - |
io.servicecomb.foundation.ssl.SSLCustom implementation | No | Specifies
implementation of the SSLCustom class, which is used by developers to convert
passwords and file paths. | - |
+| ssl.sslCustomClass | - |
org.apache.servicecomb.foundation.ssl.SSLCustom implementation | No |
Specifies implementation of the SSLCustom class, which is used by developers to
convert passwords and file paths. | - |
> **NOTE:**
>
@@ -138,5 +138,5 @@ ssl.keyStore: server.p12
ssl.keyStoreType: PKCS12
ssl.keyStoreValue: Changeme_123
ssl.crl: revoke.crl
-ssl.sslCustomClass: io.servicecomb.demo.DemoSSLCustom
+ssl.sslCustomClass: org.apache.servicecomb.demo.DemoSSLCustom
```
diff --git a/_users/zuul.md b/_users/zuul.md
index 154eeac..8cd6cd5 100644
--- a/_users/zuul.md
+++ b/_users/zuul.md
@@ -60,7 +60,7 @@ This topic describes how to start a ZuulProxy application as
the API Gateway. Pe
<artifactId>spring-cloud-starter-hystrix</artifactId>
</dependency>
<dependency>
- <groupId>io.servicecomb</groupId>
+ <groupId>org.apache.servicecomb</groupId>
<artifactId>spring-boot-starter-discovery</artifactId>
</dependency>
```
----------------------------------------------------------------
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:
[email protected]
With regards,
Apache Git Services
