dubbo/dubbo-demo
crazyhzm 0f61286a78 Merge branch '3.2' into 3.3
# Conflicts:
#	dubbo-dependencies-bom/pom.xml
2023-09-20 15:32:19 +08:00
..
dubbo-demo-annotation Bump org.springframework.boot:spring-boot-maven-plugin (#12965) 2023-08-29 09:44:43 +08:00
dubbo-demo-api Merge branch 'apache-3.2' into apache-3.3 2023-08-31 18:59:20 +08:00
dubbo-demo-generic-call Use bom mode flatten (#12239) 2023-05-08 07:42:49 +08:00
dubbo-demo-interface Correcting spelling mistakes (#12480) 2023-06-09 10:29:27 +08:00
dubbo-demo-native Bump org.graalvm.buildtools:native-maven-plugin from 0.9.26 to 0.9.27 (#13070) 2023-09-20 09:42:35 +08:00
dubbo-demo-spring-boot Merge branch '3.2' into 3.3 2023-09-20 15:32:19 +08:00
dubbo-demo-triple skip demo javadoc (#12411) 2023-05-28 15:07:30 +08:00
dubbo-demo-xml Bump org.springframework.boot:spring-boot-maven-plugin (#12965) 2023-08-29 09:44:43 +08:00
README.md Add -jar for java command in dubbo-demo readme file (#4517) 2019-07-10 13:27:11 +08:00
pom.xml Remove dubbo-bom self used (#12252) 2023-05-08 09:35:59 +08:00

README.md

Dubbo Demo

This directory contains basic usages of Dubbo to help Dubbo developers for debugging and smoke test purpose. If you are looking for Dubbo samples for study purpose, you should look into here where you will find comprehensive usages for how to use Dubbo in different scenarios with the different features.

How To Build

To build all demo applications from the source code, simply step into 'dubbo-demo' directory and use maven to build:

mvn clean package

After build completes, a couple of fat jars are generated under 'target' directory under each module directories, for example: 'dubbo-demo-api-provider-${project.version}.jar' can be found under the directory 'dubbo-demo/dubbo-demo-api/dubbo-demo-api-provider/target'.

How To Run

Since the generated artifacts are fat jars backed by spring boot maven plugin, they can be executed directly with 'java -jar', and since multicast is used for service registration, a necessary system property '-Djava.net.preferIPv4Stack=true' is required in order to registry and discover the demo service properly.

Use 'dubbo-demo/dubbo-demo-api' as an example, to start the provider 'dubbo-demo-api-provider', execute the following command:

java -Djava.net.preferIPv4Stack=true -jar dubbo-demo-api-provider-${project.version}.jar

To run the consumer 'dubbo-demo-api-consumer', execute the following command:

java -Djava.net.preferIPv4Stack=true -jar dubbo-demo-api-consumer-${project.version}.jar